View AD9739-R2-EBZ_8821722.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

14-bit, 2.5 gsps, rf digital-to-analog converter data sheet ad9739 rev. b information furnished by analog devices is believed to be accurate and reliable. however, no responsibility is assumed by analog devices for its use, nor for any infringements of patents or other rights of third parties that may result from its use. specifications subject to change without notice. no license is granted by implication or otherwise under any patent or patent rights of analog devices. trademarks and registered trademarks are the property of their respective owners. one technology way, p.o. box 9106, norwood, ma 02062-9106, u.s.a. tel: 781.329.4700 www.analog.com fax: 781.461.3113 ?2009C2012 analog devices, inc. all rights reserved. features direct rf synthesis at 2.5 gsps update rate dc to 1.25 ghz in baseband mode 1.25 ghz to 3.0 ghz in mix mode industry leading single/multicarrier if or rf synthesis f out = 350 mhz, aclr =80 dbc f out = 950 mhz, aclr = 78 dbc f out = 2100 mhz, aclr = 69 dbc dual-port lvds data interface up to 1.25 gsps operation source synchronous ddr clocking pin-compatible with the ad9739a multichip synchronization capability programmable output current: 8.7 ma to 31.7 ma low power: 1.16 w at 2.5 gsps applications broadband communications systems military jammers instrumentation, automatic test equipment radar, avionics general description the ad9739 is a 14-bit, 2.5 gsps high performance rf digital- to-analog converter (dac) capable of synthesizing wideband signals from dc up to 3.0 ghz. its dac core features a quad- switch architecture that provides exceptionally low distortion performance with an industry-leading direct rf synthesis capability. this feature enables multicarrier generation up to the nyquist frequency in baseband mode as well as second and third nyquist zones in mix mode. the output current can be programmed over the 8.66 ma to 31.66 ma range. the inclusion of on-chip controllers simplifies system integration. a dual-port, source synchronous, lvds interface simplifies the digital interface with existing fgpa/asic technology. on-chip controllers are used to manage external and internal clock domain variations over temperature to ensure reliable data transfer from the host to the dac core. multichip synchronization is possible with an on-chip synchronization controller. a serial peripheral interface (spi) is used for device configuration as well as readback of status registers. the ad9739 is manufactured on a 0.18 m cmos process and operates from 1.8 v and 3.3 v supplies. it is supplied in a 160-ball chip scale ball grid array for reduced package parasitics. functional block diagram lvds ddr receiver dci sdo sdio sclk cs dacclk dco sync_out sync_in db0[13:0] db1[13:0] clk distribution (div-by-4) data controller 4-to-1 data assembler spi reset lvds ddr receiver sync- controller data latch ioutp ioutn vref i120 irq 1.2v dac bias ad9739 txdac core dll (mu controller) 07851-001 figure 1. product highlights 1. ability to synthesize high quality wideband signals with bandwidths of up to 1.25 ghz in the first or second nyquist zone. 2. a proprietary quad-switch dac architecture provides exceptional ac linearity performance while enabling mix mode operation. 3. a dual-port, double data rate, lvds interface supports the maximum conversion rate of 2500 msps. 4. on-chip controllers manage external and internal clock domain skews. 5. a multichip synchronization capability. 6. programmable differential current output with a 8.66 ma to 31.66 ma range.
ad9739 data sheet rev. b | page 2 of 48 table of contents features .............................................................................................. 1 ? applications....................................................................................... 1 ? general description ......................................................................... 1 ? functional block diagram .............................................................. 1 ? product highlights ........................................................................... 1 ? revision history ............................................................................... 2 ? specifications..................................................................................... 4 ? dc specifications ......................................................................... 4 ? lvds digital specifications ........................................................ 5 ? serial port specifications ............................................................. 6 ? ac specifications.......................................................................... 7 ? absolute maximum ratings............................................................ 8 ? thermal resistance ...................................................................... 8 ? esd caution.................................................................................. 8 ? pin configurations and function descriptions ........................... 9 ? typical performance characteristics ........................................... 12 ? ac (normal mode).................................................................... 12 ? ac (mix mode) .......................................................................... 15 ? terminology .................................................................................... 17 ? serial port interface (spi) register............................................... 18 ? spi register map description................................................... 18 ? spi operation.............................................................................. 18 ? spi register map............................................................................. 20 ? spi port configuration and software reset............................ 22 ? power-down lvds interface and txdac?............................ 22 ? controller clock disable........................................................... 22 ? interrupt request (irq) enable/status ................................... 22 ? txdac full-scale current setting (i outfs ) and sleep ........... 23 ? txdac quad-switch mode of operation .............................. 23 ? dci phase alignment status .................................................... 23 ? sync_in phase alignment status .......................................... 23 ? data receiver controller configuration................................. 23 ? data receiver controller_data sample delay value ............ 24 ? data and sync receiver controller_dci delay value/window and phase rotation......................................... 24 ? data receiver controller_delay line status and sync controller sync_out status ................................................. 24 ? sync and data receiver controller lock/tracking status.... 25 ? clk input common mode ...................................................... 25 ? mu controller configuration and status................................ 25 ? part id ......................................................................................... 26 ? theory of operation ...................................................................... 27 ? lvds data port interface.......................................................... 28 ? mu controller ............................................................................. 32 ? interrupt requests...................................................................... 34 ? multiple device synchronization............................................. 35 ? analog interface considerations.................................................. 38 ? analog modes of operation ..................................................... 38 ? clock input considerations...................................................... 39 ? voltage reference ....................................................................... 40 ? analog outputs .......................................................................... 40 ? nonideal spectral artifacts....................................................... 43 ? lab evaluation of the ad9739 ................................................. 44 ? power dissipation and supply domains................................. 44 ? recommended start-up sequence .......................................... 45 ? outline dimensions ....................................................................... 48 ? ordering guide .......................................................................... 48 ? revision history 1/12rev. a to rev. b changes to features section, applications section, general description section, figure 1, product highlights section........ 1 changes to dc specifications section........................................... 4 changed digital specifications section to lvds digital specifications section....................................................................... 5 changes to lvds digital specifications section ......................... 5 added serial port specifications section and table 3; renumbered sequentially................................................................ 6 changes to ac specifications section ........................................... 7 changes to table 5............................................................................ 8 changes to table 7.......................................................................... 10 deleted static linearity section and figure 7 to figure 17; renumbered sequentially ............................................................. 11 changed dynamic performance normal mode, 20 ma full scale (unless otherwise noted) section to ac (normal mode) section.............................................................................................. 12 changes to ac (normal mode) section ..................................... 12 changed dynamic performance mix mode, 20 ma full scale section to ac (mix mode) section.............................................. 15 changes to ac (mix mode) section............................................ 15 added serial port interface (spi) register section, spi register map description section, reset section, table 8, and spi operation section and figure 34 ................................................. 18
data sheet ad9739 rev. b | page 3 of 48 deleted docsis performance section and figure 46 to figure 72 .....................................................................19 added figure 35 through figure 38; renumbered sequentially....19 changes to spi register map section and table 9......................20 added spi port configuration and software reset section, power-down lvds interface and txdac? section, controller clock disable section, interrupt request (irq) enable/status section, and table 10 to table 13 ..................................................22 added txdac full-scale current setting (i outfs ) and sleep section, txdac quad-switch mode of operation section, dci phase alignment status section, sync_in phase alignment status section, data receiver controller configuration section, and table 14 to table 18 .................................................................23 added data receiver controller_data sample delay value section, data and sync receiver controller_dci delay value/window and phase rotation section, data receiver controller_delay line status and sync controller sync_out status section, and table 19 to table 21.......................................24 deleted serial peripheral interface section, general operation of the serial interface section, instruction mode (8-bit instruction) section, and serial interface port pin description section .......25 added sync and data receiver controller lock/tracking status section, clk input common mode section, mu controller configuration and status section, and table 22 to table 24.....25 deleted msb/lsb transfers section, serial port configuration section, and figure 74 to figure 79 ..............................................26 added part id section and table 25 ............................................26 changes to theory of operation section ....................................27 added figure 39 ..............................................................................27 deleted spi registers section and table 8 to table 31...............28 moved and changes to lvds data port interface section .......28 added figure 40 and figure 41 .....................................................28 changes to figure 42 ......................................................................29 moved and changes to figure 43..................................................29 added data receiver controller initialization description section, table 26, and data receiver operation at lower clock rates section ....................................................................................30 added lvds driver and receiver input section, figure 44 to figure 47, and table 27...................................................................31 changed and moved mu delay controller section to mu controller section ...........................................................................32 changes to mu controller section, figure 48, and figure 49...32 added figure 50 and table 28 .......................................................32 added mu controller initialization description section..........33 changes to interrupt requests section ........................................34 added table 29 ................................................................................34 changed synchronization controller section to multiple device synchronization section....................................................35 added figure 52 ..............................................................................35 changes to figure 53 ......................................................................36 added sync controller initialization description section........36 added synchronization limitations section...............................37 changed applications information to analog interface considerations section...................................................................38 changes to analog modes of operation section .......................38 deleted clocking the ad9739 section, figure 85, and figure 86..39 added clock input considerations section, figure 58 to figure 60...........................................................................................39 deleted clock phase noise affects on ac performance section, table 32 to table 34, applying data to the ad9739 section, and figure 87...........................................................................................40 moved figure 61..............................................................................40 changes to voltage references section and analog outputs section ..............................................................................................40 added equivalent dac output and transfer function and figure 63...........................................................................................40 deleted mu control operation section, search mode section, and figure 89 ...................................................................................41 moved figure 64..............................................................................41 added peak dac output power capability section and figure 65. 41 deleted figure 90, figure 91, track mode section, mu delay and phase readback section, operating the mu controller manually section, and calculating mu delay line step size section ..............................................................................................42 added output stage configuration section and figure 66 to figure 70...........................................................................................42 added nonideal spectral artifacts section, figure 71, and table 30.............................................................................................43 deleted operation in master mode, figure 93, and figure 94...........................................................................................44 added lab evaluation of the ad9739 section, power dissipation and supply domains section, and figure 72 to figure 74.........44 deleted figure 95, operation in slave mode section, and data receiver operation in auto mode section..................................45 changes to recommended start-up sequence section ............45 added figure 75 ..............................................................................45 deleted figure 97, data receiver operation in manual mode section, calculating the dci delay line step size section, and maximum allowable data timing skew/jitter section.............46 added table 31 ................................................................................46 deleted optimizing the clock common-mode voltage section, figure 99, analog control registers section, mirror roll-off frequency control section, and figure 101................................47 added table 32 ................................................................................47 deleted figure 103, figure 104, and figure 106 .........................48 updated outline dimensions........................................................48 deleted figure 107 to figure 109 ..................................................49 deleted table 35 to table 44 ..........................................................50 7/11rev 0 to rev a changes to table 2, dac clock input (dacclk_p, dacclk_n), added dac clock rate .........................................4 changes to table 3, added dynamic performance parameters....... 5 change to ordering guide ............................................................53 2/09revision 0: initial release
ad9739 data sheet rev. b | page 4 of 48 specifications dc specifications vdda = vdd33 = 3.3 v, vddc = vdd = 1.8 v, i outfs = 20 ma. table 1. parameter min typ max unit resolution 14 bits accuracy integral nonlinearity (inl) 1.3 lsb differential nonlinearity (dnl) 0.8 lsb analog outputs gain error (with internal reference) 5.5 % full-scale output current 8.66 20.2 31.66 ma output compliance range ?1.0 +1.0 v common-mode output resistance 10 m differential output resistance 70 output capacitance 1 pf dac clock input (dacclk_p, dacclk_n) differential peak-to-peak voltage 1.2 1.6 2.0 v common-mode voltage 900 mv dac clock rate 0.8 2.5 ghz temperature drift gain 60 ppm/c reference voltage 20 ppm/c reference internal reference voltage 1.15 1.2 1.25 v output resistance 5 k analog supply voltages vdda 3.1 3.3 3.5 v vddc 1.70 1.8 1.90 v digital supply voltages vdd33 3.10 3.3 3.5 v vdd 1.70 1.8 1.90 v supply currents and power dissipation, 2.0 gsps i vdda 37 38 ma i vddc 159 166 ma i vdd33 34 37 ma i vdd 233 238 ma power dissipation 0.940 0.975 w sleep mode, i vdda 2.5 2.75 ma power-down mode (register 0x01 = 0x33 and register 0x02 = 0x80) i vdda 0.02 ma i vddc 3.8 ma i vdd33 0.5 ma i vdd 0.1 ma supply currents and power dissipation, 2.5 gsps i vdda 37 ma i vddc 223 ma i vdd33 34 ma i vdd 290 ma power dissipation 1.16 w
data sheet ad9739 rev. b | page 5 of 48 lvds digital specifications vdda = vdd33 = 3.3 v, vddc = vdd = 1.8 v, i outfs = 20 ma. lvds drivers and receivers are compliant to the ieee standard 1596.3- 1996 reduced range link, unless otherwise noted. table 2. parameter min typ max unit lvds data inputs (db0[13:0], db1[13:0]) 1 input common-mode voltage range, v com 825 1575 mv logic high differential input threshold, v ih_dth 175 400 mv logic low differential input threshold, v il_dth ?175 ?400 mv receiver differential input impedance, r in 80 120 input capacitance 1.2 pf lvds input rate 1250 msps lvds minimum data valid period, t valid (see figure 41 ) 344 ps lvds clock input (dci and sync_in) 2 input common-mode voltage range, v com 825 1575 mv logic high differential input threshold, v ih_dth 175 400 mv logic low differential input threshold, v il_dth ?175 ?400 mv receiver differential input impedance, r in 80 120 input capacitance 1.2 pf maximum clock rate 625 mhz lvds clock output (dco and sync_out) 3 output voltage high (x_p or x_n) 1375 mv output voltage low (x_p or x_n) 1025 mv output differential voltage, |v od | 150 200 250 mv output offset voltage, v os 1150 1250 mv output impedance, single-ended, r o 80 100 120 r o single-ended mismatch 10 % maximum clock rate 625 mhz 1 db0[x]p, db0[x]n, db1[x]p, and db1[x]n pins. 2 dci_p and dci_n pins, as well as sync_in_p and sync_in_n pins. 3 dco_p and dco_n pins, as well as sync_out_p/sync_out_n pins with 100 differential termination.
ad9739 data sheet rev. b | page 6 of 48 serial port specifications vdda = vdd33 = 3.3 v, vddc = vdd = 1.8 v. table 3 . parameter min typ max unit write operation (see figure 36 ) sclk clock rate, f sclk (or /t sclk ) 20 mhz sclk clock high, t hi 18 ns sclk clock low, t low 18 ns sdio to sclk setup time, t ds 2 ns sclk to sdio hold time, t dh 1 ns cs to sclk setup time, t s 3 ns sclk to cs hold time, t h 2 ns read operation (see figure 37 and figure 38 ) sclk clock rate, f sclk (or /t sclk ) 20 mhz sclk clock high, t hi 18 ns sclk clock low, t low 18 ns sdio to sclk setup time, t ds 2 ns sclk to sdio hold time, t dh 1 ns cs to sclk setup time, t s 3 ns sclk to sdio (or sdo) data valid time, t dv 15 ns cs to sdio (or sdo) output valid to high-z, t ez 2 ns inputs (sdio, sclk, cs ) voltage in high, v ih 2.0 3.3 v voltage in low, v il 0 0.8 v current in high, i ih ?10 +10 a current in low, i il ?10 +10 a output (sdio) voltage out high, v oh 2.4 3.5 v voltage out low, v ol 0 0.4 v current out high, i oh 4 ma current out low, i ol 4 ma
data sheet ad9739 rev. b | page 7 of 48 ac specifications vdda = vdd33 = 3.3 v, vddc = vdd = 1.8 v, i outfs = 20 ma, f dac = 2400 msps. table 4. parameter min typ max unit dynamic performance dac clock rate 800 2500 msps adjusted dac update rate 1 800 2500 msps output settling time (t st ) to 0.1% 13 ns spurious-free dynamic range (sfdr) f out = 100 mhz 69.5 dbc f out = 350 mhz 58.5 dbc f out = 550 mhz 54 dbc f out = 950 mhz 60 dbc two-tone intermodulation distortion (imd), f out2 = f out1 + 1.25 mhz f out = 100 mhz 94 dbc f out = 350 mhz 78 dbc f out = 550 mhz 72 dbc f out = 950 mhz 68 dbc noise spectral density (nsd), 0 dbfs single tone f out = 100 mhz ?166 dbm/hz f out = 350 mhz ?161 dbm/hz f out = 550 mhz ?160 dbm/hz f out = 850 mhz ?160 dbm/hz wcdma aclr (single carrier), adjacent/alternate adjacent channel f dac = 2457.6 msps f out = 350 mhz 80/80 dbc f dac = 2457.6 msps, f out = 950 mhz 78/79 dbc f dac = 2457.6 msps, f out = 1700 mhz (mix mode) 74/74 dbc f dac = 2457.6 msps, f out = 2100 mhz (mix mode) 69/72 dbc 1 adjusted dac updated rate is calculated as f dac divided by the minimum requir ed interpolation factor. for the ad9739, the minimum interpol ation factor is 1. thus, with f dac = 2500 msps, f dac adjusted = 2500 msps.
ad9739 data sheet rev. b | page 8 of 48 absolute maximum ratings table 5. parameter with respect to rating vdda vssa ?0.3 v to +3.6 v vdd33 vss ?0.3 v to +3.6 v vdd vss ?0.3 v to +1.98 v vddc vssc ?0.3 v to +1.98 v vssa vss ?0.3 v to +0.3 v vssa vssc ?0.3 v to +0.3 v vss vssc ?0.3 v to +0.3 v dacclk_p, dacclk_n vssc ?0.3 v to vddc + 0.18 v dci, dco, sync_in, sync_out vss ?0.3 v to vdd33 + 0.3 v lvds data inputs vss ?0.3 v to vdd33 + 0.3 v ioutp, ioutn vssa ?1.0 v to vdda + 0.3 v i120, vref vssa ?0.3 v to vdda + 0.3 v irq, cs , sclk, sdo, sdio, reset vss ?0.3 v to vdd33 + 0.3 v junction temperature 150c storage temperature ?65c to +150c stresses above those listed under absolute maximum ratings may cause permanent damage to the device. this is a stress rating only; functional operation of the device at these or any other conditions above those indicated in the operational section of this specification is not implied. exposure to absolute maximum rating conditions for extended periods may affect device reliability. thermal resistance ja is specified for the worst-case conditions, that is, a device soldered in a circuit board for surface-mount packages. table 6. thermal resistance package type ja jc unit 160-ball csp_bga 31.2 7.0 c/w 1 1 with no airflow movement. esd caution
data sheet ad9739 rev. b | page 9 of 48 pin configurations and function descriptions a b c d e f g h j k l m n p 1413 12 11 10 876 32 19 54 vssa, analog supply ground vssa shield, analog supply ground shield vdda, 3.3v, analog supply 07851-002 figure 2. analog supply pins (top view) a b c d e f g h j k l m n p 141312 11 10 876 32 19 54 vss digital supply ground vdd33, 3.3v digital supply vdd, 1.8v, digital supply 07851-003 figure 3. digital supply pins (top view) a b c d e f g h j k l m n p 1413 12 11 10 876 32 19 54 vssc, clock supply ground vddc, 1.8v, clock supply 07851-004 figure 4. digital lvds clock supply pins (top view) a b c d e f g h j k l m sync_out_p/_n db1[0:13]p db1[0:13]n db0[0:13]p db0[0:13]n differential input signal (clock or data) sync_in_p/_n dacclk_n dacclk_p n p 141312 11 10 876 32 19 54 dci_p/_n dco_p/_n 07851-005 figure 5. digital lvds input, clock i/o (top view)
ad9739 data sheet rev. b | page 10 of 48 a b c d e f g h j k l m n p 141312 11 10 876 32 19 54 irq cs sclk reset sdio sdo ioutn ioutp i120 vref iptat 07851-006 figure 6. analog i/o and spi control pins (top view) table 7 . ad9739 pin function descriptions pin no. mnemonic description c1, c2, d1, d2, e1, e2, e3, e4 vddc 1.8 v clock supply input. a1, a2, a3, a4, a5, b1, b2, b3, b4, b5, c4, c5, d4, d5 vssc clock supply return. a10, a11, b10, b11, c10, c11, d10, d 11 vdda 3.3 v analog supply input. a12, a13, b12, b13, c12, c13, d12, d13, vssa analog supply return. a6, a9, b6, b9, c6, c9, d6, d9, f1, f2, f3, f4, e11, e12, e13, e14, f11, f12 vssa shield analog supply return shield. tie to vssa at the dac. a14 nc no connect. do not connect to this pin. a7, b7, c7, d7 ioutn dac negative current output source. a8, b8, c8, d8 ioutp dac positive current output source. b14 i120 nominal 1.2 v reference. tie to analog ground via a 10 k resistor to generate a 120 a reference current. c14 vref voltage reference input/output. decouple to vssa with a 1 nf capacitor. d14 nc factory test pin. do not connect to this pin. c3, d3 dacclk_n/dacclk_p negative/positive dac clock input (dacclk). f13 irq interrupt request open drain output. active high. pull up to vdd33 with a 10 k resistor. f14 reset reset input. active high. tie to vss if unused. g13 cs serial port enable input. g14 sdio serial port data input/output. h13 sclk serial port clock input. h14 sdo serial port data output. j3, j4, j11, j12 vdd33 3.3 v digital supply input. g1, g2, g3, g4, g11, g12 vdd 1.8 v digital supply. input. h1, h2, h3, h4, h11, h12, k3, k4, k11, k12 vss digital supply return. j1, j2 sync_out_p/sync_out_n positive/negative sync output (sync_out) k1, k2 sync_in_p/sync_in_n positive/negative sync input (sync_in) j13, j14 dco_p/dco_n positive/negative data clock output (dco). k13, k14 dci_p/dci_n positive/negative data clock input (dci). l1, m1 db1[0]p/db1[0]n port 1 posi tive/negative data input bit 0. l2, m2 db1[1]p/db1[1]n port 1 posi tive/negative data input bit 1. l3, m3 db1[2]p/db1[2]n port 1 posi tive/negative data input bit 2. l4, m4 db1[3]p/db1[3]n port 1 posi tive/negative data input bit 3. l5, m5 db1[4]p/db1[4]n port 1 posi tive/negative data input bit 4. l6, m6 db1[5]p/db1[5]n port 1 posi tive/negative data input bit 5.
data sheet ad9739 rev. b | page 11 of 48 pin no. mnemonic description l7, m7 db1[6]p/db1[6]n port 1 posi tive/negative data input bit 6. l8, m8 db1[7]p/db1[7]n port 1 posi tive/negative data input bit 7. l9, m9 db1[8]p/db1[8]n port 1 posi tive/negative data input bit 8. l10, m10 db1[9]p/db1[9]n port 1 posi tive/negative data input bit 9. l11, m11 db1[10]p/db1[10]n port 1 positive/negative data input bit 10. l12, m12 db1[11]p/db1[11]n port 1 positive/negative data input bit 11. l13, m13 db1[12]p/db1[12]n port 1 positive/negative data input bit 12. l14, m14 db1[13]p/db1[13]n port 1 positive/negative data input bit 13. n1, p1 db0[0]p/db0[0]n port 0 posi tive/negative data input bit 0. n2, p2 db0[1]p/db0[1]n port 0 posi tive/negative data input bit 1. n3, p3 db0[2]p/db0[2]n port 0 posi tive/negative data input bit 2. n4, p4 db0[3]p/db0[3]n port 0 posi tive/negative data input bit 3. n5, p5 db0[4]p/db0[4]n port 0 posi tive/negative data input bit 4. n6, p6 db0[5]p/db0[5]n port 0 posi tive/negative data input bit 5. n7, p7 db0[6]p/db0[6]n port 0 posi tive/negative data input bit 6. n8, p8 db0[7]p/db0[7]n port 0 posi tive/negative data input bit 7. n9, p9 db0[8]p/db0[8]n port 0 posi tive/negative data input bit 8. n10, p10 db0[9]p/db0[9]n port 0 posi tive/negative data input bit 9. n11, p11 db0[10]p/db0[10]n port 0 positive/negative data input bit 10. n12, p12 db0[11]p/db0[11]n port 0 positive/negative data input bit 11. n13, p13 db0[12]p/db0[12]n port 0 positive/negative data input bit 12. n14, p14 db0[13]p/db0[13]n port 0 positive/negative data input bit 13.
ad9739 data sheet rev. b | page 12 of 48 typical performance characteristics ac (normal mode) i outfs = 20 ma, nominal supplies, 25c, unless otherwise noted. vbw 10khz 10db/div stop 2.4ghz start 20mhz 07851-007 figure 7. single-tone spectrum at f out = 91 mhz, f dac = 2.4 gsps f out (mhz) sfdr (dbc) 30 35 40 45 50 55 60 65 70 75 80 0 100 200 300 400 500 600 700 800 900 1000 1100 1200 1.6gsps 1.2gsps 2.4gsps 2.0gsps 07851-008 figure 8. sfdr vs. f out over f dac nsd (dbm/hz) ?170 ?168 ?166 ?164 ?162 ?160 ?158 ?156 ?154 ?152 ? 150 1.2gsps 2.4gsps f out (mhz) 0 100 200 300 400 500 600 700 800 900 1000 1100 1200 07851-009 figure 9. single-tone nsd over f out vbw 10khz 10db/div stop 2.4ghz start 20mhz 07851-010 figure 10. single-tone spectrum at f out = 1091 mhz, f dac = 2.4 gsps f out (mhz) imd (dbc) 30 0 100 200 300 400 500 600 700 800 900 1000 35 40 45 50 55 60 65 70 75 80 85 90 95 100 1100 1200 1.2gsps 1.6gsps 2.0gsps 2.4gsps 07851-011 figure 11. imd vs. f out over f dac f out (mhz) nsd (dbm/hz) 0 100 200 300 400 500 600 700 800 900 1000 1100 1200 ?170 ?169 ?168 ?167 ?166 ?165 ?164 ?163 ?162 ?161 ? 160 2.4gsps 1.2gsps 07851-012 figure 12. eight-tone nsd over f out
data sheet ad9739 rev. b | page 13 of 48 f dac = 2 gsps, i outfs = 20 ma, nominal supplies, 25c, unless otherwise noted. ?3dbfs 0dbfs f out (mhz) sfdr (dbc) 30 40 50 60 70 80 90 0 100 200 300 400 500 600 700 800 900 1000 ?6dbfs 07851-013 figure 13. sfdr vs. f out over digital full scale f out (mhz) sfdr (db) 30 0 100 200 300 400 500 600 700 800 900 1000 40 50 60 70 80 90 0dbfs ?3dbfs ?6dbfs 07851-014 figure 14. sfdr for second harmonic over f out vs. digital full scale f out (mhz) sfdr (dbc) 30 40 50 60 70 80 90 0 100 200 300 400 500 600 700 800 900 1000 10ma fs 20ma fs 30ma fs 07851-015 figure 15. sfdr vs. f out over dac i outfs f out (mhz) imd (dbc) 30 40 50 60 70 80 90 100 110 0 100 200 300 400 500 600 700 800 900 1000 0dbfs ?6dbfs ?3dbfs 07851-016 figure 16. imd vs. f out over digital full scale f out (mhz) sfdr (db) 30 0 100 200 300 400 500 600 700 800 900 1000 40 50 60 70 80 90 ?6dbfs ?3dbfs 0dbfs 0 7851-017 figure 17. sfdr for third harmonic over f out vs. digital full scale f out (mhz) imd (dbc) 30 40 50 60 70 80 90 100 110 0 100 200 300 400 500 600 700 800 900 1000 10ma fs 20ma fs 30ma fs 07851-018 figure 18. imd vs. f out over dac i outfs
ad9739 data sheet rev. b | page 14 of 48 f out (mhz) sfdr (dbc) 30 40 50 60 70 80 90 0 100 200 300 400 500 600 700 800 900 1000 +25c +85c ?40c 07851-019 figure 19. sfdr vs. f out over temperature ?170 ?168 ?166 ?164 ?162 ?160 ?158 ?156 ?154 ?152 ? 150 0 200 400 600 800 1000 100 300 500 700 900 f out (mhz) nsd (dbm/hz) +25c ?40c +85c 07851-020 figure 20. single-tone nsd vs. f out over temperature vbw 300khz 10db/div span 53.84mhz sweep 174.6ms (601pts) center 350.27mhz #res bw 30khz rms results carrier power ?14.54dbm/ 3.84mhz freq offset (mhz) 5 10 15 20 25 ref bw (mhz) 3.84 3.84 3.84 3.84 3.84 (dbc) ?79.90 ?80.60 ?80.90 ?80.62 ?80.76 (dbm) ?94.44 ?95.14 ?95.45 ?95.16 ?95.30 lower (dbc) ?79.03 ?79.36 ?80.73 ?80.97 ?80.95 (dbm) ?93.57 ?94.40 ?95.27 ?95.51 ?95.49 upper 07851-021 figure 21. single-carrier wcdma at 350 mhz, f dac = 2457.6 msps f out (mhz) imd (dbc) 30 40 50 60 70 80 90 100 110 0 100 200 300 400 500 600 700 800 900 1000 +25c ?40c +85c 07851-022 figure 22. imd vs. f out over temperature ?170 ?168 ?166 ?164 ?162 ?160 ?158 ?156 ?154 ?152 ? 150 0 200 400 600 800 1000 100 300 500 700 900 f out (mhz) nsd (dbm/hz) +25c ?40c +85c 07851-023 figure 23. eight-tone nsd vs. f out over temperature ?90 ?85 ?80 ?75 ?70 ?65 ?60 ?55 ? 50 0 122.88 245.76 368.64 491.52 614.40 737.28 860.16 983.04 1105.90 1228.80 first adj ch second adj ch fifth adj ch f out (mhz) aclr (dbc) 07851-024 figure 24. four-carrier wcdma at 350 mhz, f dac = 2457.6 msps
data sheet ad9739 rev. b | page 15 of 48 ac (mix mode) f dac = 2.4 gsps, i outfs = 20 ma, nominal supplies, 25c, unless otherwise noted. vbw 10khz 10db/div stop 2.4ghz sweep 28.7s (601pts) start 20mhz #res bw 10khz 07851-025 figure 25. single-tone spectrum at f out = 2.31 ghz, f dac = 2.4 gsps 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 1200 1300 1400 1500 1600 1700 1800 1900 2000 2100 2200 2300 2400 f out (mhz) sfdr (dbc) 07851-026 figure 26. sfdr in mix mode vs. f out at 2.4 gsps vbw 300khz 10db/div span 53.84mhz sweep 174.6ms (601pts) center 2.10706mhz #res vw 30khz rms results carrier power ?21.43dbm/ 3.84mhz freq offset (mhz) 5 10 15 20 25 ref bw (mhz) 3.84 3.84 3.84 3.84 3.84 (dbc) ?68.99 ?72.09 ?72.86 ?74.34 ?74.77 (dbm) ?90.43 ?93.52 ?94.30 ?95.77 ?96.20 lower (dbc) ?63.94 ?71.07 ?71.34 ?72.60 ?73.26 (dbm) ?90.37 ?92.50 ?92.77 ?94.03 ?94.70 upper 07851-027 figure 27. typical single-carrier wc dma aclr performance at 2.1 ghz, f dac = 2457.6 msps (second nyquist zone) vbw 10khz 10db/div stop 2.4ghz start 20mhz stop 2.4ghz sweep 28.7s (601pts) start 20mhz #res bw 10khz 07851-028 figure 28. single-tone spectrum in mix mode at f out = 1.31 ghz, f dac = 2.4 gsps 30 35 40 45 50 55 60 65 70 75 80 85 90 1200 1300 1400 1500 1600 1700 1800 1900 2000 2100 2200 2300 2400 f out (mhz) imd (dbc) 07851-029 figure 29. imd in mix mode vs. f out at 2.4 gsps ?90 ?85 ?80 ?75 ?70 ?65 ?60 ?55 ?50 ?45 ? 40 1229 1475 1720 1966 2212 2458 2703 2949 3195 3441 3686 second nyquist zone third nyquist zone first adj ch second adj ch fifth adj ch f out (mhz) aclr (dbc) 07851-030 figure 30. single-carrier wcdma aclr vs. f out at 2457.6 msps
ad9739 data sheet rev. b | page 16 of 48 vbw 300khz 10db/div span 53.84mhz sweep 174.6ms (601pts) center 2.807ghz #res bw 30khz rms results carrier power ?24.4dbm/ 3.84mhz freq offset (mhz) 5 10 15 20 25 ref bw (mhz) 3.84 3.84 3.84 3.84 3.84 (dbc) ?64.90 ?66.27 ?68.44 ?70.20 ?70.85 (dbm) ?89.30 ?90.67 ?92.84 ?94.60 ?95.25 lower (dbc) ?63.82 ?65.70 ?66.55 ?68.95 ?70.45 (dbm) ?88.22 ?90.10 ?90.95 ?93.35 ?94.85 upper 07851-031 figure 31. typical single-carrier wc dma aclr performance at 2.8 ghz, f dac = 2457.6 msps (third nyquist zone) vbw 300khz 10db/div span 63.84mhz sweep 207ms (601pts) center 2.09758ghz #res bw 30khz rms results carrier power ?25.53dbm/ 3.84mhz freq offset (mhz) 5 10 15 20 25 30 ref bw (mhz) 3.84 3.84 3.84 3.84 3.84 3.84 (dbc) 0.22 ?66.68 ?68.01 ?68.61 ?68.87 ?69.21 (dbm) ?25.31 ?92.21 ?93.53 ?94.14 ?94.40 ?94.74 lower (dbc) 0.24 0.14 ?66.82 ?67.83 ?67.64 ?68.50 (dbm) ?25.29 ?25.38 ?92.35 ?93.36 ?93.17 ?94.03 upper 07851-032 figure 32. typical four-carrier wcdma aclr performance at 2.1 ghz, f dac = 2457.6 msps (second nyquist zone) vbw 300khz 10db/div span 63.84mhz sweep 207ms (601pts) center 2.81271ghz #res bw 30khz rms results carrier power ?27.98dbm/ 3.84mhz freq offset (mhz) 5 10 15 20 25 30 ref bw (mhz) 3.84 3.84 3.84 3.84 3.84 3.84 (dbc) ?0.42 ?64.32 ?66.03 ?66.27 ?66.82 ?67.16 (dbm) ?28.40 ?92.30 ?94.01 ?94.24 ?94.79 ?95.13 lower (dbc) ?0.10 ?0.08 ?65.37 ?66.06 ?63.36 ?66.54 (dbm) ?28.07 ?28.06 ?93.34 ?94.03 ?93.34 ?94.51 upper 07851-033 figure 33. typical four-carrier wcdma aclr performance at 2.8 ghz, f dac = 2457.6 msps (third nyquist zone)
data sheet ad9739 rev. b | page 17 of 48 terminology linearity error (integral nonlinearity or inl) the maximum deviation of the actual analog output from the ideal output, determined by a straight line drawn from 0 to full scale. differential nonlinearity (dnl) the measure of the variation in analog value, normalized to full scale, associated with a 1 lsb change in digital input code. monotonicity a dac is monotonic if the output either increases or remains constant as the digital input increases. offset error the deviation of the output current from the ideal of 0 is called the offset error. for ioutp, 0 ma output is expected when the inputs are all 0s. for ioutn, 0 ma output is expected when all inputs are set to 1. gain error the difference between the actual and ideal output span. the actual span is determined by the output when all inputs are set to 1 minus the output when all inputs are set to 0. output compliance range the range of allowable voltage at the output of a current output dac. operation beyond the maximum compliance limits may cause either output stage saturation or breakdown, resulting in nonlinear performance. temp er atu re d r i f t specified as the maximum change from the ambient (25c) value to the value at either t min or t max . for offset and gain drift, the drift is reported in ppm of full-scale range (fsr) per c. for reference drift, the drift is reported in ppm per c. power supply rejection (psr) the maximum change in the full-scale output as the supplies are varied from nominal to minimum and maximum specified voltages. spurious-free dynamic range (sfdr) the difference, in decibels (db), between the rms amplitude of the output signal and the peak spurious signal over the specified bandwidth. total harmonic distortion (thd) the ratio of the rms sum of the first six harmonic components to the rms value of the measured input signal. it is expressed as a percentage or in decibels (db). noise spectral density (nsd) nsd is the converter noise power per unit of bandwidth. this is usually specified in dbm/hz in the presence of a 0 dbm full-scale signal. adjacent channel leakage ratio (aclr) the adjacent channel leakage (power) ratio is a ratio, in dbc, of the measured power within a channel relative to its adjacent channels. modulation error ratio (mer) modulated signals create a discrete set of output values referred to as a constellation. each symbol creates an output signal corresponding to one point on the constellation. mer is a measure of the discrepancy between the average output symbol magnitude and the rms error magnitude of the individual symbol. intermodulation distortion (imd) imd is the result of two or more signals at different frequencies mixing together. many products are created according to the formula, af1 bf2, where a and b are integer values.
ad9739 data sheet rev. b | page 18 of 48 s erial port interface (spi) register s pi register map description the ad9739 contains a set of programmable registers described in table 10 that are used to configure and monitor various internal parameters. note the following points when programming the ad9739 spi registers: ? registers pertaining to similar functions are grouped together and assigned adjacent addresses. ? bits that are undefined within a register should be assigned a 0 when writing to that register. ? registers that are undefined should not be written to. ? a hardware or software reset is recommended upon power-up to place spi registers in a known state. ? a spi initialization routine is required as part of the boot process. see table 31 and table 32 for example procedures. reset issuing a hardware or software reset places the ad9739 spi registers in a known state. all spi registers (excluding 0x00) are set to their default states as described in table 10 upon issuing a reset. after issuing a reset, the spi initialization process need only write to registers that are required for the boot process as well as any other register settings that must be modified, depending on the target application. although the ad9739 does feature an internal power-on-reset (por), it is still recommended that a software or hardware reset be implemented shortly after power-up. the internal reset signal is derived from a logical or operation from the internal por signal, the reset pin, and the software reset state. a software reset can be issued via the reset bit (register 0x00, bit 5) by toggling the bit high then low. note that, because the msb/lsb format may still be unknown upon initial power-up (that is, internal por is unsuccessful), it is also recommended that the bit settings for bits[7:5] be mirrored onto bits[2:0] for the instruction cycle that issues a software reset. a hardware reset can be issued from a host or external supervisory ic by applying a high pulse with a minimum width of 40 ns to the reset pin (that is, pin f14). reset should be tied to vss if unused. table 8. spi registers pertaining to spi options address (hex) bit description 7 enable 3-wire spi 6 enable spi lsb first 0x00 5 software reset spi operation the serial port of the ad9739 shown in figure 34 has a 3- or 4-wire spi capability, allowing read/write access to all registers that configure the devices internal parameters. it provides a flexible, synchronous serial communications port, allowing easy interface to many industry-standard microcontrollers and microprocessors. the 3.3 v serial i/o is compatible with most synchronous transfer formats, including the motorola? spi and the intel? ssr protocols. sdo (pin h14) sdio (pin g14) sclk (pin h13) cs (pin g13) ad9739 spi port 07851-034 figure 34. ad9739 spi port the default 4-wire spi interface consists of a clock (sclk), serial port enable ( cs ), serial data input (sdio), and serial data output (sdo). the inputs to sclk, cs , and sdio contain a schmitt trigger with a nominal hysteresis of 0.4 v centered about vdd33/2. the maximum frequency for sclk is 20 mhz. the sdo pin is active only during the transmission of data and remains three- stated at any other time. a 3-wire spi interface can be enabled by setting the sdio_dir bit (register 0x00, bit 7). this causes the sdio pin to become bidirectional such that output data only appears on the sdio pin during a read operation. the sdo pin remains three-stated in a 3-wire spi interface. instruction header information msb lsb 17 16 15 14 13 12 11 10 r/ w a6 a5 a4 a3 a2 a1 a0 an 8-bit instruction header must accompany each read and write operation. the msb is a r/ w indicator bit with logic high indicating a read operation. the remaining seven bits specify the address bits to be accessed during the data transfer portion. the eight data bits immediately follow the instruction header for both read and write operations. for write operations, registers change immediately upon writing to the last bit of each transfer byte. cs can be raised after each sequence of eight bits (except the last byte) to stall the bus. the serial transfer resumes when cs is lowered. stalling on nonbyte boundaries resets the spi.
data sheet ad9739 rev. b | page 19 of 48 the ad9739 serial port can support both most significant bit (msb) first and least significant bit (lsb) first data formats. figure 35 illustrates how the serial port words are formed for the msb first and lsb first modes. the bit order is controlled by the sdio_dir bit (register 0x00, bit 7). the default value is 0, msb first. when the lsb first bit is set high, the serial port interprets both instruction and data bytes lsb first. sclk sdata sclk sdata r/w r/w a1 a3 a2 a4 n1 n1 n2 n2 a0 a3 a1 a2 a0 a4 d7 1 d0 1 d1 1 d6 n d7 n d6 1 d1 n d0 n data transfer cycle instruction cycle data transfer cycle instruction cycle cs cs 07851-035 figure 35. spi timing, msb first (upper) and lsb first (lower) figure 36 illustrates the timing requirements for a write operation to the spi port. after the serial port enable ( cs ) signal goes low, data (sdio) pertaining to the instruction header is read on the rising edges of the clock (sclk). to initiate a write operation, the read/not-write bit is set low. after the instruction header is read, the eight data bits pertaining to the specified register are shifted into the sdio pin on the rising edge of the next eight clock cycles. figure 37 illustrates the timing for a 3-wire read operation to the spi port. after cs goes low, data (sdio) pertaining to the instruction header is read on the rising edges of sclk. a read operation occurs if the read/not-write indicator is set high. after the address bits of the instruction header are read, the eight data bits pertaining to the specified register are shifted out of the sdio pin on the falling edges of the next eight clock cycles. figure 38 illustrates the timing for a 4-wire read operation to the spi port. the timing is similar to the 3-wire read operation with the exception that data appears at the sdo pin only, while the sdio pin remains at high impedance throughout the operation. the sdo pin is an active output only during the data transfer phase and remains three-stated at all other times. d7 d6 a0 d1 n1 n0 t s sclk sdio 1/ f sclk t low t hi t ds t dh r/w d0 t h cs 0 7851-036 figure 36. spi write operation timing d7 d6 a0 d1 n1 t s s clk sdio 1/ f sclk t low t hi t ds t dh r/w d0 t ez a2 a1 t dv cs 07851-037 figure 37. spi 3-wire re ad operation timing a0 cs n1 t s sclk sdio 1/ f sclk t low t hi t ds t dh r/w t ez a2 a1 t dv d7 d6 d1 sdo d0 t ez 07851-038 figure 38. spi 4-wire read operation timing
ad9739 data sheet rev. b | page 20 of 48 spi register map table 9. full register map (n/a = not applicable) name hex addr bit 7 bit 6 bit 5 bit 4 bi t 3 bit 2 bit 1 bit 0 default mode 00 sdio_dir lsb/msb reset n/a n/a n/a n/a n/a 0x00 power- down 01 n/a n/a lvds_ drvr_pd lvds_ rcvr_pd n/a n/a clk_ rcvr_pd dac_ bias_pd 0x00 cnt_ clk_dis 02 n/a n/a n/a n/a clkgen_pd n/a rec_cnt_ clk mu_cnt_ clk 0x03 irq_en 03 n/a n/a sync_ lst_en sync_ lck_en mu_lst_en mu_lck_en rcv_ lst_en rcv_ lck_en 0x00 irq_req 04 n/a n/a sync_ lst_irq sync_ lck_irq mu_lst_ irq mu_lck_ irq rcvlst_ irq rcvlck_ irq 0x00 rsvd 05 n/a n/a n/a n/a n/a n/a n/a n/a n/a fsc_1 06 fsc[7] fsc[6] fsc[5] fsc[4] fsc[3] fsc[2] fsc[1] fsc[0] 0x00 fsc_2 07 sleep n/a n/a n/a n/a n/a fsc[9] fsc[8] 0x02 dec_ cnt 08 n/a n/a n/a n/a n/a n/a dac_dec[1] dac_dec[0] 0x00 rsvd 09 n/a n/a n/a n/a n/a n/a n/a n/a n/a lvds_ cnt 0a n/a n/a n/a n/a hndoff_ chk_rst n/a lvds_ bias[1] lvds_ bias[0] 0x00 dig_ stat 0b hndoff_ fall[3] hndoff_ fall[2] hndoff_ fall[1] hndoff_ fall[0] hndoff_ rise[3] hndoff_ rise[2] hndoff_ rise[1] hndoff_ rise[0] rndm lvds_ stat1 0c sup/hld_ edge1 n/a dci_ phs3 dci_ phs1 dci_pre_ ph2 dci_pre_ ph0 dci_pst_ ph2 dci_pst_ ph0 rndm lvds_ stat2 0d sup/hld_ sync sup/hld_ edge0 sync_ samp1 sync_ samp0 lvds1_hi lvds1_lo lvds0_hi lvds0_lo rndm/0 rsvd 0e n/a n/a n/a n/a n/a n/a n/a n/a n/a rsvd 0f n/a n/a n/a n/a n/a n/a n/a n/a n/a lvds_ rec_ cnt1 10 sync_ flg_rst sync_ loop_on sync_ mst/slv sync_ cnt_ena n/a rcvr_ flg_rst rcvr_ loop_on rcvr_ cnt_ena 0x42 lvds_ rec_ cnt2 11 smp_del[1] smp_ del[0] fine_ del_ mid[3] fine_ del_ mid[2] fine_del_ mid[1] fine_del_ mid[0] rcvr_ gain[1] rcvr_ gain[0] 0xdd lvds_ rec_ cnt3 12 smp_del[9] smp_ del[8] smp_ del[7] smp_ del[6] smp_ del[5] smp_ del[4] smp_ del[3] smp_ del[2] 0x29 lvds_ rec_ cnt4 13 dci_del[3] dci_ del[2] dci_ del[1] dci_ del[0] fine_del_ skw[3] fine_del_ skw[2] fine_del_ skw[1] fine_del_ skw[0] 0x71 lvds_ rec_ cnt5 14 clkdivph[1] clkdivph[0] dci_ del[9] dci_ del[8] dci_ del[7] dci_ del[6] dci_ del[5] dci_ del[4] 0x0a lvds_ rec_ cnt6 15 sync_ gain[1] sync_ gain[0] syncout_ ph[1] syncout_ ph[0] lckthr[3] lckthr[2] lckthr[1] lckthr[0] 0x42 lvds_ rec_ cnt7 16 n/a synco_ del[6] synco_ del[5] synco_ del[4] synco_ del[3] synco_ del[2] synco_ del[1] synco_ del[0] 0x00 lvds_ rec_ cnt8 17 syncsh_ del[0] n/a n/a n/a n/a n/a n/a n/a 0x00 lvds_ rec_ cnt9 18 syncsh_ del[8] syncsh_ del[7] syncsh_ del[6] syncsh_ del[5] syncsh_ del[4] syncsh_ del[3] syncsh_ del[2] syncsh_ del[1] 0x00 lvds_ rec_ stat1 19 smp_del[1] smp_del[0] n/a n/a smp_ fine_ del[3] smp_ fine_ del[2] smp_ fine_ del[1] smp_ fine_ del[0] 0xc7 lvds_ rec_ stat2 1a smp_del[9] smp_ del[8] smp_ del[7] smp_ del[6] smp_ del[5] smp_ del[4] smp_ del[3] smp_ del[2] 0x29
data sheet ad9739 rev. b | page 21 of 48 name hex addr bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 default lvds_ rec_ stat3 1b dci_del[1] dci_del[0] n/a n/a syncout ph[1] syncout ph[0] clkdiv ph[1] clkdiv ph[0] 0xc0 lvds_ rec_ stat4 1c dci_del[9] dci_ del[8] dci_ del[7] dci_ del[6] dci_ del[5] dci_ del[4] dci_ del[3] dci_ del[2] 0x29 lvds_ rec_ stat5 1d fine_del_ pst[3] fine_del_ pst[2] fine_del_ pst[1] fine_del_ pst[0] fine_del_ pre[3] fine_del_ pre[2] fine_del_ pre[1] fine_del_ pre[0] 0x86 lvds_ rec_ stat6 1e n/a synco_ del[6] synco_ del[5] synco_ del[4] synco_ del[3] synco_ del[2] synco_ del[1] synco_ del[0] 0x00 lvds_ rec_ stat7 1f syncsh_ del[0] n/a n/a n/a n/a n/a n/a n/a 0x00 lvds_ rec_ stat8 20 syncsh_ del[8] syncsh_ del[7] syncsh_ del[6] syncsh_ del[5] syncsh_ del[4] syncsh_ del[3] syncsh_ del[2] syncsh_ del[1] 0x00 lvds_ rec_ stat9 21 sync_ trk_on sync_ init_on sync_ lst_lck sync_lck rcvr_ trk_on rcvr_ fe_on rcvr_lst rcvr_lck 0x00 cross_ cnt1 22 n/a n/a n/a dir_p clkp_ offset[3] clkp_ offset[2] clkp_ offset[1] clkp_ offset[0] 0x00 cross_ cnt2 23 n/a n/a n/a dir_n clkn_ offset[3] clkn_ offset[2] clkn_ offset[1] clkn_ offset[0] 0x00 phs_ det 24 n/a n/a cmp_bst phs_det auto_en bias[3] bias[2] bias[1] bias[0] 0x00 mu_ duty 25 mu_ dutyauto_en pos/neg adj[5] adj[4] adj[3] adj[2] adj[1] adj[0] 0x00 mu_ cnt1 26 n/a slope mode[1] mode[0] read gain[1] gain[0] enable 0x42 mu_ cnt2 27 mudel[0] srch_mode [1] srch_mode [0] set_phs[4] set_phs[3] set_phs[ 2] set_phs[1] setphs[0] 0x40 mu_ cnt3 28 mudel[8] mudel[7] mudel[6] mudel[5] mu del[4] mudel[3] mudel[2] mudel[1] 0x00 mu_ cnt4 29 search_tol retry contrst guard[4] guar d[3] guard[2] guard[ 1] guard[0] 0x0b mu_ stat1 2a n/a n/a n/a n/a n/a n/a mu_lost mu_lkd 0x00 rsvd 2b n/a n/a n/a n/a n/a n/a n/a n/a n/a rsvd 2c n/a n/a n/a n/a n/a n/a n/a n/a n/a ana_ cnt1 32 hdrm[7] hdrm[6] hdrm[5] hdrm[4] hdrm[3] hdrm[2] hdrm[1] hdrm[0] 0xca ana_ cnt2 33 n/a n/a n/a n/a n/a n/a msel[1] msel[0] 0x03 rsvd 34 n/a n/a n/a n/a n/a n/a n/a n/a n/a part id 35 id[7] id[6] id[5] id[4] id[3] id[2] id[1] id[0] 0x20
ad9739 data sheet rev. b | page 22 of 48 spi port configuration and software reset table 10. spi port configuration and software reset register address (hex) name bit r/w default setting comments sdio_dir 7 r/w 0 0 = 4-wire spi, 1 = 3-wire spi. lsb/msb 6 r/w 0 0 = msb first, 1 = lsb first. 0x00 reset 5 r/w 0 software reset is recommended before modification of other spi registers from the default setting. setting the bit to 1 causes all registers (except 0x00) to be set to the default setting. setting the bit to 0 corresponds to the inactive state, allowing the user to modify registers from the default setting. power-down lvds interface and txdac? table 11. power-down lvds interface and txdac register address (hex) name bit r/w default setting comments lvds_drvr_pd 5 r/w 0 lvds_rcvr_pd 4 r/w 0 clk_rcvr_pd 1 r/w 0 0x01 dac_bias_pd 0 r/w 0 power-down of the lvds drivers/receivers and txdac. 0 = enable, 1 = disable. controller clock disable table 12. controller clock disable register address (hex) name bit r/w default setting comments clkgen_pd 3 r/w 0 internal clk distribution enable: 0 = enable, 1 = disable. rec_cnt_clk 1 r/w 1 0x02 mu_cnt_clk 0 r/w 1 lvds receiver and mu controller clock disable. 0 = disable, 1 = enable. interrupt request (irq) enable/status table 13. interrupt request (irq) enable/status register address (hex) name bit r/w default setting comments sync_lst_en 5 w 0 sync_lck_en 4 w 0 mu_lst_en 3 w 0 mu_lck_en 2 w 0 rcv_lst_en 1 w 0 0x03 rcv_lck_en 0 w 0 this register enables the sync, mu, and lvds rx controllers to update their corresponding irq status bits in register 0x04, which defines whether the controller is locked (lck) or unlocked (lst). 0 = disable (resets the status bit). 1 = enable. sync_lst_irq 5 r 0 sync_lck_irq 4 r 0 mu_lst_irq 3 r 0 mu_lck_irq 2 r 0 rcv_lst_irq 1 r 0 0x04 rcv_lck_irq 0 r 0 this register indicates the status of the controllers. for lck_iqr bits: 0 = lost locked, 1 = locked. for lst_iqr bits: 0 = not lost locked, 1 = unlocked. note that, if the controller irq is serviced, the relevant bits in register 0x03 should be reset by writing 0, followed by another write of 1 to enable.
data sheet ad9739 rev. b | page 23 of 48 txdac full-scale current setting (i outfs ) and sleep table 14. txdac full-scale current setting (i outfs ) and sleep register address (hex) name bit r/w default setting comments 0x06 fsc_1 [7:0] r/w 0x00 fsc_2 [1:0] r/w sets the txdac i outfs current between 8 ma and 31 ma (default = 20 ma). i outfs = 0.0226 fsc[9:0] + 8.58, where fsc = 0 to 1023. 0x07 sleep 7 r/w 0x02 0 = enable dac output, 1 = disable dac output (sleep). txdac quad-switch mode of operation table 15. txdac quad-switch mode of operation register address (hex) name bit r/w default setting comments 0x08 dac-dec [1:0] r/w 0x00 0x00 = normal baseband mode. 0x01 = return-to-zero mode. 0x02 = mix mode. dci phase alignment status table 16. dci phase alignment status register address (hex) name bit r/w default setting comments dci_pre_ph0 2 r 0 0 = dci rising edge is after the pre dela yed version of the phase 0 sampling edge. 1 = dci rising edge is before the pre dela yed version of the phase 0 sampling edge. 0x0c dci_pst_ph0 0 r 0 0 = dci rising edge is after the post dela yed version of the phase 0 sampling edge. 1 = dci rising edge is before the post de layed version of the phase 0 sampling edge. sync_in phase alignment status table 17. sync_in phase alignment status register address (hex) name bit r/w default setting comments sync_in_ph90 5 r 0 0 = syncin rising edge is after phase 90 sampling edge. 1 = syncin rising edge is before phase 90 sampling edge. 0x0d sync_in_ph0 4 r 0 0 = syncin rising edge is after phase 0 sampling edge. 1 = syncin rising edge is before phase 0 sampling edge. data receiver controller configuration table 18. data receiver controller configuration register address (hex) name bit r/w default setting comments sync_flg_rst 7 w 0 sync controller flag reset. write 1 followed by 0 to reset flags. sync_loop_on 6 r/w 1 0 = disable, 1 = enable. enable for master only. when enabled, sync controller generates an irq when master falls out of lock and automatically begins search/track routine. sync_mst/slv 5 r/w 0 sync controller configuration. 0 = slave, 1 = master. sync_cnt_ena 4 r/w 0 sync controller enable. 0 = disable, 1 = enable rcvr_flg_rst 2 w 0 data receiver controller flag reset. write 1 followed by 0 to reset flags. rcvr_loop_on 1 r/w 1 0 = disable, 1 = enable. when enabled, the data receiver controller generates an irq; it falls out of lock and automatically begins a search/track routine. 0x10 rcvr_cnt_ena 0 r/w 0 data receiver contro ller enabled. 0 = disable, 1 = enable.
ad9739 data sheet rev. b | page 24 of 48 data receiver controller_ data sample delay value table 19. data receiver controller_ data sample delay value register address (hex) name bit r/w default setting comments 0x11 smp_del[1:0] [7:6] r/w 11 0x12 smp_del[9:2] [7:0] r/w 0x25 controller enabled: the 10-bit value (wit h a maximum of 332) represents the start value for the delay line used by the state ma chine to sample data. leave at the default setting of 167, which represents the midpoint of the delay line. controller disabled: the value sets the actual value of the delay line. data and sync receiver controller_dci delay value/window and phase rotation table 20. data and sync receiver controller_dci delay value/window and phase rotation register address (hex) name bit r/w default setting comments dci_del[3:0] [7:4] r/w 0111 refer to the dci_del description in register 0x14. 0x13 fine_del_skew [3:0] r/w 0001 a 4-bit value sets the difference (that is, window) for the dci pre and post sampling clocks. leave at the default value of 1 for a narrow window. clkdivph[1:0] [7:6] r/w 00 relative phase of internal div-by-4 circuit. this feature allows phase rotation in 90 increments (that is, 1 count) to extend rx controllers locking range for clock rates between 0.8 gsps to 1.6 gsps (only valid with sync controller disabled). 0x14 dci_del[9:4] [5:0] r/w 001010 controller enabled: the 10-bit value (wit h a maximum of 332) represents the start value for the delay line used by the state machine to sample the dci input. leave at the default setting of 167, which represents the midpoint of the delay line. controller disabled: the value sets the actual value of the delay line. sync gain[1:0] [7:6] r/w 00 sets the sync tracking gain (optimal value is 1). syncout_ph[1:0] [5:4] r/w 00 readback of the present sync_out phase selection. 0x15 lckthr[3:0] [3:0] r/w 0000 sets the difference between the sample and dci delays to lock (optimal value is 2). 0x16 synco_del[6:0] [6:0] r/w 0x00 sets the sync output delay value when the synch controller is disabled; otherwise, is the read status of the sync outp ut delay value when sync is enabled. 0x17 syncsh_del[0] [7] r/w 0x00 sets the sync setup and hold delay value when the synch controller is disabled; otherwise, is the read status of sync setup and hold value when sync is enabled. 0x18 syncsh_del[8:1] [7:0] r/w 0x00 sets the sync setup and hold delay value when the synch controller is disabled; otherwise, is the read status of sync setup and hold value when sync is enabled. data receiver controller_delay line stat us and sync controller sync_out status table 21. data receiver controller_delay line stat us and sync controller sync_out status register address (hex) name bit r/w default setting comments 0x19 smp_del[1:0] [7:6] r 00 0x1a smp_del[9:2] [7:0] r 0x00 syncout_ph[1:0] 3:2 r 00 clkdiv ph[1:0] 1:0 r 00 0x1b dci_del[1:0] [7:6] r 00 0x1c dci_del[9:2] [7:0] r 0x00 the actual value of the dci and data delay lines determined by the data receiver controller (when enabled) after the state machine completes its search and enters track mode. note that these values should be equal. syncout_ph provides phase status (0/ 90/180/270) of phase select mux, while clkdivph provides phase status of data receiver controller (register 0x14).
data sheet ad9739 rev. b | page 25 of 48 sync and data receiver cont roller lock/tracking status table 22. sync and data receiver controller lock/tracking status register address (hex) name bit r/w default setting comments sync_trk_on 7 r 0 sync_lst 5 r 0 sync_lck 4 r 0 rcvr_trk_on 3 r 0 rcvr_lst 1 r 0 0x21 rcvr_lck 0 r 0 sync_trk_on and rcvr_trk_on: 0 = tracking not established. 1 = tracking established. sync_lck and rcvr_lck: 0 = controller is not locked. 1 = controller is locked. sync_lst and rcvr_lst: 0 = lock has not been lost. 1 = lock has been lost at some point. clk input common mode table 23. clk input common mode register address (hex) name bit r/w default setting comments dir_p 4 r/w 0 0x22 clkp_offset[3:0] [3:0] r/w 0000 dir_n 4 r/w 0 0x23 clkn_offset[3:0] [3:0] r/w 0000 dir_p and dir_n: 0 = vcm at the dacclk_p input decreases with the offset value. 1 = vcm at the dacclk_p input increases with the offset value. clkx_offset sets the magnitude of the offset for the dacclk_p and dacclk_n inputs. for optimum performance, set to 1111. mu controller configuration and status table 24. mu controller configuration and status register address (hex) name bit r/w default setting comments cmp_bst 5 r/w 0 0x24 phs_det auto_en 4 r/w 0 phase detector enable and boost bias bits. note that both bits should always be set to 1 to enable these functions. 0x25 mu_duty auto_en 7 r/w 0 mu controller duty cycle enable. note that this bit should always be set to 1 to enable. slope 6 r/w 1 mu controller phase slope lock. 0 = negative slope, 1 = positive slope. refer to table 28 for optimum setting. 0x26 mode[1:0] [5:4] r/w 00 sets the mu controller mode of operation. 00 = search and track (recommended). 01 = search only. 10 = track. read 3 r/w 0 set to 1 to read the current value of the mu delay line in. gain[1:0] [2:1] r/w 01 sets the mu controller tracking gain. recommended to leave at the default 01 setting. enable 0 r/w 0 1 = enable the mu controller. 0 = disable the mu controller. mudel[0] 7 r/w 0 the lsb of the 9-bit mudel setting. srch_mode[1:0] [6:5] r/w 0 sets the direction in which the mu controller searches (from its initial mudel setting) for the optimum mu delay line setting that corresponds to the desired phase/slope setting (that is, set_phs and slope ). 00 = down. 01 = up. 10 = down/up (recommended). 0x27 set_phs[4:0] [4:0] r/w 0 sets the target phase that the mu controller locks to with a maximum setting of 16. refer to table 28 for optimum setting.
ad9739 data sheet rev. b | page 26 of 48 address (hex) name bit r/w default setting comments w 0x00 with enable (bit 0, register 0x26) set to 0, this 9-bit value represents the value that the mu delay is set to. note that the maximum value is 432. with enable set to 1, this value repr esents the mu delay value at which the controller begins its search. setting this value to the delay line midpoint of 216 is recommended. 0x28 mudel[8:1] [7:0] r 0x00 when read (bit 3, register 0x26) is set to 1, the value read back is equal to the value written into the register when enable = 0 or the value that the mu controller locks to when enable = 1. search_tol 7 r/w 0 0 = not exact (can find a phase within two values of the desired phase). 1 = finds the exact phase that is targeted (optimal setting). retry 6 r/w 0 0 = stop the search if the correct value is not found. 1 = retry the search if the correct value is not found. contrst 5 r/w 0 controls whether the controller resets or continues when it does not find the desired phase. 0 = continue (optimal setting). 1 = reset. 0x29 guard[4:0] 4 r/w 01011 sets a guard band from the beginning and end of the mu delay line which the mu controller does not enter into unless it does not find a valid phase outside the guard band (optimal value is decimal 11 or 0x0b). mu_lst 1 r 0 0 = mu controller has not lost lock. 1 = mu controller has lost lock. 0x2a mu_lkd 0 r 0 0 = mu controller is not locked. 1= mu controller is locked. part id table 25. part id register address (hex) name bit r/w default setting comments 0x35 part_id [7:0] r 0x20 part id number.
data sheet ad9739 rev. b | page 27 of 48 theory of operation the ad9739 data receiver controller generates an internal sampling clock offset by 90 from the dci to sample the input data on the db0 and db1 ports. when enabled and configured properly for track mode, it ensures proper data recovery between the host and the ad9739 clock domains. the data receiver controller has the ability to track several hundreds of ps of drift between these clock domains, typically caused by supply and temperature variation. figure 39 shows a top-level functional diagram of the ad9739. a high performance txdac core delivers a signal dependent, differential current (nominal 10 ma) to a balanced load referenced to ground. the frequency of the clock signal appearing at the ad9739 differential clock receiver, dacclk, sets the txdacs update rate. this clock signal, which serves as the master clock, is routed directly to the txdac as well as to a clock distribution block that generates all critical internal and external clocks. as mentioned, the host processor provides the ad9739 with a deinterleaved data stream such that the db0 and db1 data ports receive alternating samples (that is, odd/even data streams). the ad9739 data assembler is used to reassemble (that is, multiplex) the odd/even data streams into their original order before delivery into the txdac for signal reconstruction. the pipeline delay from a sample being latched into the data port to when it appears at the dac output is on the order of 78 () dacclk cycles. applications that require matching pipeline delays (that is, synchronization) between multiple ad9739 s can use the sync controller. the sync controller phase aligns the outputs of one or more ad9739 devices (that is,. sl aves) to a master ad9739 device. lvds ddr receiver dci sdo sdio sclk cs dacclk dco sync_out sync_in db0[13:0] db1[13:0] clk distribution (div-by-4) data controller 4-to-1 data assembler spi reset lvds ddr receiver sync- controller data latch ioutp ioutn vref i120 irq 1.2v dac bias ad9739 txdac core dll (mu controller) 07851-039 the ad9739 includes a delay lock loop (dll) circuit controlled via a mu controller to optimize the timing hand-off between the ad9739 digital clock domain and txdac core. besides ensuring proper data reconstruction, the txdacs ac performance is also dependent on this critical hand-off between these clock domains with speeds of up to 2.5 gsps. once properly initialized and configured for track mode, the dll maintains optimum timing alignment over temperature, time, and power supply variation. figure 39. functional block diagram of the ad9739 a spi interface is used to configure the various functional blocks as well as monitor their status for debug purposes. proper operation of the ad9739 requires that controller blocks be initialized upon power-up. a simple spi initialization routine is used to configure the controller blocks (see figure 51 and figure 52 ). an irq output signal is available to alert the host should any of the controllers fall out of lock during normal operation. the ad9739 includes two 14-bit lvds data ports (db0 and db1) to reduce the data interface rate to ? the txdac update rate. the host processor drives deinterleaved data with offset binary format onto the db0 and db1 ports, along with an embedded dci clock that is synchronous with the data. because the interface is double data rate (ddr), the dci clock is essentially an alternating 010101.01010 bit pattern with a frequency equal to ? the txdac update rate (f dac ). to simplify synchronization with the host processor, the ad9739 passes an lvds clock output (dco) that is also equal to the dci frequency. the following sections discuss the various functional blocks in more detail as well as their implications when interfacing to external ics and circuitry. while a detailed description of the various controllers (and associated spi registers used to configure and monitor) is also included for completeness, the recommended spi boot procedure can be used to ensure reliable operation.
ad9739 data sheet rev. b | page 28 of 48 lvds data port interface the ad9739 supports input data rates from 1.6 gsps to 2.5 gsps using dual lvds data ports. the interface is source synchronous and double data rate (ddr) where the host provides an embedded data clock input (dci) at f dac /4 with its rising and falling edges aligned with the data transitions. the data format is offset binary; however, twos complement format can be realized by reversing the polarity of the msb differential trace. as shown in figure 40 , the host feeds the ad9739 with deinterleaved input data into two 14-bit lvds data ports (db0 and db1) at ? the dac clock rate (that is, f dac /2). the ad9739 internal data receiver controller then generates a phase shifted version of dci to register the input data on both the rising and falling edges. lvds ddr receiver dci dco db0[13:0] div-by-4 data controller lvds ddr receiver db1[13:0] ad9739 host processor lvds ddr driver 14 2 f data = f dac /2 f dco = f dac /4 f dac f dci = f dac /4 14 2 1 2 1 2 data deinterleaver even data samples odd data samples 07851-040 figure 40. recommended digital interface between the ad9739 and host processor as shown in figure 41 , the dci clocks edges must be coincident with the data bit transitions with minimum skew, jitter, and intersymbol interference. to ensure coincident transitions with the data bits, the dci signal should be implemented as an additional data line with an alternating (010101) bit sequence from the same output drivers used for the data. maximizing the opening of the eye in both the dci and data signals improves the reliability of the data port interface. differential controlled impedance traces of equal length (that is, delay) should also be used between the host processor and ad9739 input to limit bit-to-bit skew. the maximum allowable skew and jitter out of the host processor with respect to the dci clock edge on each lvds port is calculated as maxskew + jitter = period(ns) ? validwindow (ps) ? guard = 800 ps ? 344 ps ? 100 ps = 356 ps where validwindow (ps) is represented by t va l i d and guard is represented by t guard in figure 41 . the minimum specified lvds va lid window is 344 ps, and a guard band of 100 ps is recommended. therefore, at the maximum operating frequency of 2.5 gsps, the maximum allowable fpga and pcb bit skew plus jitter is equal to 356 ps. for synchronous operation, the ad9739 provides a data clock output, dco, to the host at the same rate as dci (that is, f dac /4) to maintain the lowest skew variation between these clock domains. since the dco signal is generated from a separate clock divider, its phase relationship relative to the f dac /4 clocks used by the data receiver controller will vary upon each power-up. applications sensitive to this phase ambiguity (resulting in a 2 dacclk pipeline variation) should consider using the sync controller. the host processor has a worst-case skew between dco and dci that is both implementation and process dependent. this worst-case skew can also vary an additional 30% over temperature and supply corners. the delay line within the data receiver controller can track a 1.5 ns skew variation after initial lock. while it is possible for the host to have an internal pll that generates a synchronous f dac /4 from which the dci signal is derived, digital implementations that result in the shortest propagation delays result in the lowest skew variation. the data receiver controller is used to ensure proper data hand-off between the host and ad9739 internal digital clock domains. the circuit shown in figure 42 functions as a delay lock loop in which a 90 o phase shifted version of the dci clock input is used to sample the input data into the ddr receiver registers. this ensures that the sampling instance occurs in the middle of the data pattern eyes (assuming matched dci and dbx[13:0] delays). note that, because the dci delay and sample delay clocks are derived from the div-by-4 circuitry, this 90 phase relationship holds as long as the delay settings (that is, dci_del, smp_del) are also matched. db0[13:0] a nd db1[13:0] dci t valid t valid + t guard 2 1 /f dac max skew + jitter 07851-041 figure 41. lvds data port timing requirements
data sheet ad9739 rev. b | page 29 of 48 fine delay ddr ff dbx[13:1] data receiver controller dci delay sample delay dci pre post sample dci window pre dci window post dci window sample data to core delay delay fine delay fine delay state machine/ tracking loop elastic fifo ddr ff ddr ff ddr ff ddr ff 180 0 f dac div-by-4 to sync controller phase rotation from sync controller or spi reg 0x14, bit[7:6] 90 270 delay delay ddr ff ddr ff dci delay path sample delay path dco div-by-4 07851-042 figure 42. top level diagram of the data receiver controller the div-by-4 circuit generates four clock phases that serve as inputs to the data receiver controller. all of the ddr registers in the data and dci paths operate on both clock edges; however, for clarity purposes, only the phases (that is, 0 o and 90 o ) corresponding to the positive edge of each path are shown. one of the div-by-4 phases is used to generate the dco signal; therefore, the phase relationship between dco and clocks fed into the controller remains fixed. note that it is this attribute that allows possible factory calibration of images and clock spurs attributed to f dac /4 modulation of the critical dac clock. once this data has been successively sampled into the first set of registers, an elastic fifo is used to transfer the data into the ad9739 clock domain. to continuously track any phase variation between the two clock domains, the data receiver controller should always be enabled and placed into track mode (register 0x10, bit 1 and bit 0). tracking mode operates continuously in the background to track delay variations between the host and ad9739 clock domains. it does so by ensuring that the dci signal is sampled within a very narrow window defined by two internally generated clocks (that is, pre and pst), as shown in figure 43 . proper sampling of the dci signal can also be confirmed by monitoring the status of dci_pre_ph0 (register 0x0c, bit 2) and dci_pst_ph0 (register 0x0c, bit 0). if the delay settings are correct, the state of dci_ pre_ph0 should be 0, and the state of dci_pst_ph0 should be 1. note that the states of these status bits may toggle occasionally due to cycle-to cycle jitter exceeding the window width. however, the controller averages these status bits over multiple clock cycles to ensure that the dci signal falls within a programmable window. dci fine delay pst fine delay pre fine_del_skew 07851-043 figure 43. pre- and post-delay sampling diagram the skew or window width (fine_del_skew) is set via register 0x13, bits[3:0], with a maximum skew of approximately 180 ps and resolution of 12 ps. it is recommended that the skew be set to 36 ps (that is, register 0x13 = 0x72) during initialization. the skew setting also affects the speed of the controller loop, with tighter skew settings corresponding to longer response time.
ad9739 data sheet rev. b | page 30 of 48 da ta receiver controller initialization description th e data controller should be initialized and placed into track mode as the second step in the spi boot sequence. the following steps are recommended for the initialization of the data receiver controller: 1. set fine_del_skew to 2 for a larger dci sampling window (register 0x13 = 0x72). note that the default dci_del and smp_del settings of 167 are optimum. 2. disable the controller before enabling (that is, register 0x10 = 0x00). 3. enable the rx controller in two steps: register 0x10 = 0x02 followed by register 0x10 = 0x03. 4. wait 135k clock cycles. 5. read back register 0x21 and confirm that it is equal to 0x05 to ensure that the dll loop is locked and tracking. 6. include this step for operation <1.6 gsps. read back the dci_del value to determine whether the value falls within a user-defined tracking guard band. if it does not, rotate clkdivph by 1 (register 0x14, bits[7:6] and go back to step 2. once the controller is enabled during the initial spi boot process (see table 31 and table 32 ), the controller enters a search mode where it seeks to find the closest rising edge of the dci clock (relative to a delayed version of an internal f dac /4 clock) by simultaneously adjusting the delays in the clocks used to register the dci and data inputs. a state machine searches above and below the initial dci_del value. the state machine first searches for the first rising edge above the dci_del and then searches for the first rising edge below the dci_del value. the state machine selects the closest rising edge and then enters track mode. it is recommended that the default midscale delay setting (that is, decimal 167) for the dci_del and smp_del bits be kept to ensure that the selected edge remains closest to the delay line midpoint, thus providing the greatest range for tracking timing variations and preventing the controller from falling out of lock. the adjustable delay span for these internal clocks (that is, dci and sample delay) is nominally 4 ns. the 10-bit delay value is user programmable from the decimal equivalent code (0 to 384) with approximately 12 ps/lsb resolution via the dci_del and smp_del registers (via register 0x11 thru register 0x14). when the controller is enabled, it overwrites these registers with the delay value it converges upon. the minimum difference between this delay value and the minimum/maximum values (that is, 0 and 334) represents the guard band for tracking. therefore, if the controller initially converges upon a dci_del and smp_del value between 80 and 304, the controller has a guard band of at least 80 code (approximately 1 ns) to track phase variations between the clock domains. upon initialization of the ad9739 , a certain period of time is required for the data receiver controller to lock onto the dci clock signal. note that, due to its dependency on the mu controller and synchronization controller (optional), the data receiver controller should be enabled only after these other controllers have been enabled and established locked. all of the internal controllers operate at submultiples of the dac update rate. the number of f dac clock cycles required to lock onto the dci clock is dependent on whether the synchronization controller is enabled as shown in table 26 . table 26. typical/worst-case lo ck times for lvds controller (relative to 1/f dac ) synchronization controller typical worst case off 70k 135k slave 70k 135k master 300k 560k during the spi initialization process, the user has the option of polling register 0x21 (bit 0, bit 1, and bit 3) to determine if the data receiver controller is locked, has lost lock, or has entered into track mode before completing the boot sequence. alternatively, the appropriate irq bit (register 0x03 and register 0x04) can be enabled such that an irq output signal is generated upon the controller establishing lock (see the interrupt requests section). the data receiver controller can also be configured to generate an interrupt request (irq) upon losing lock. losing lock can be caused by excessive jitter on the dci input signal, disruption of the main dac clock input, or loss of a power supply rail. to service the interrupt, the host can poll the rcvr_lck bit (register 0x21, bit 0) to determine the current state of the controller. if this bit is cleared, the search/track procedure can be restarted by setting the rcvr_loop_on bit in register 0x10, bit 1. after waiting the required lock time, the host can poll the rcvr_lck bit to see if it has been set. before leaving the interrupt routine, the rcvr_flg_rst bit (register 0x10, bit 2) should be reset by writing a high followed by a low. data receiver operation at lower clock rates at clock rates below 1.6 gsps, it is recommended to include provisions to rotate the clkdivph setting in the spi boot process. as previously mentioned, the delay line can be varied over a nominal 4 ns window. if the minimum specified clock rate of 800 msps is considered, a dci clock rate of 200 msps corresponds to a 5 ns period, thus exceeding the delay line length. therefore, it becomes possible that the initial startup phase from the div-by-4 circuit (and dco output) is such that the data receiver controller can never establish initial lock upon power up. if the clock rate is increased to 1600 msps (that is, dci clock period of 2.5 ns), the controller will always be able to find at least two dci clock edges, therefore, establish lock. however, should the dci edges fall symmetrically (equal distance) from the initial dci_del midscale setting, a guard band of 0.75 ns (that is, (4.0 ? 2.5)/2) results. rotating the clkdivph can result in an improvement in this case by skewing one of the dci edges toward the dci_del midscale value.
data sheet ad9739 rev. b | page 31 of 48 lvds inputs (no fail-safe) v p lvds receiver gnd 100 ? v n v p, n v com = (v p + v n )/2 logic bit equivalent v p v n v p v n example 1.4v 1.0v 0.4v ?0.4v 0v logic 1 logic 0 07851-046 rotating the clkdivph phase provides a means of adjusting the delay in course steps of f dac /4. for example, in the 800 msps and 1600 msps cases described above, rotating the clkdivph setting by 1 corresponds to a delay shift of 5 ns and 2.5 ns, respectively. by adding an additional step in the spi initialization routine for the data receiver controller, it becomes possible to increase the effective range of the delay line to ensure a dci_del value that falls within a reasonable guard band. lvds driver and receiver input the ad9739 features a lvds-compatible driver and receivers. the lvds driver output used for the dco and sync_out signal includes an equivalent 200 source resistor that limits its nominal output voltage swing to 200 mv when driving a 100 load. the dco output driver can be powered down via register 0x01, bit 5. an equivalent circuit is shown in figure 44 dco_n vss v dd33 dco_p v+ v+ v? v? 100 ? vcm 100 ? esd esd 07851-044 figure 46. lvds data input levels 100 ? 100 ? 100 ? v dd33 = 3.3v lvds_1 lvds_n lvds_2 v p = 1.4v r1 r2 v p = 1.4v r1 = 4.75 100/n r2 = 2.50 100/n 07851-047 figure 44. equivalent lvds output vss v dd33 dci_p dbx[13:0] p dci_n dbx[13:0]n 100 ? esd esd 07851-045 figure 45. equivalent lvds input the lvds receivers include 100 termination resistors, as shown in figure 45 . these receivers meet the ieee-1596.3-1996 reduced swing specification (with the exception of input hysteresis, which cannot be guaranteed over all process corners). figure 46 and figure 47 show an example of nominal lvds voltage levels seen at the input of the differential receiver with resulting common- mode voltage and equivalent logic level. the lvds receivers can be powered down via register 0x01, bit 4. figure 47. resistor network to bias unused lvds data inputs the ad9739 lvds inputs do not include fail-safe capability. any unused data input pins should be biased with an external network or static driver. figure 47 shows an external biasing network that can be used to place unused data bits into a known state. the resistor values for r1 and r2 are selected to establish a v p and v n of 1.4 v and 1.0 v, respectively, depending on the number of unused digital inputs, n. table 27. example of lvds input levels applied voltages resulting differential voltage resulting common-model voltage v p (v) v n (v) v p, n v com logic bit binary equivalent 1.4 1.0 +0.4 v 1.2 v 1 1.0 1.4 ?0.4 v 1.2 v 0 1.0 0.8 +200 mv 900 mv 1 0.8 1.0 ?200 mv 900 mv 0
ad9739 data sheet rev. b | page 32 of 48 mu controller a delay lock loop (dll) is used to optimize the timing between the internal digital and analog domains of the ad9739 such that data is successfully transferred into the txdac core at rates of up to 2.5 gsps. as shown in figure 48 , the dac clock is split into an analog and a digital path with the critical analog path leading to the dac core (for minimum jitter degradation) and the digital path leading to a programmable delay line. note that the output of this delay line serves as the master internal digital clock from which all other internal and external digital clocks are derived. the amount of delay added to this path is under the control of the mu controller, which optimizes the timing between these two clock domains and continuously tracks any variation (once in track mode) to ensure proper data hand-off. 14-bi t data 14-bi t data ioutp ioutn digital circuitry analog circuitry mu delay dac clock phase detector mu delay controller 07851-048 figure 48. mu delay controller block diagram the mu controller adjusts the timing relationship between the digital and analog domains via a tapped digital delay line having a nominal total delay of 864 ps. the delay value is programmable to a 9-bit resolution (that is, 0 to 432 decimal) via the mudel register, resulting in a nominal resolution of 2 ps/lsb. because a time delay maps to a phase offset for a fixed clock frequency, the control loop essentially compares the phase relationship between the two clock domains and adjusts the phase (that is, via a tapped delay line) of the digital clock such that it is at the desired fixed phase offset (set_phs) from the critical analog clock. 0 2 4 6 8 10 12 14 16 18 0 40 80 120 160 200 240 280 320 360 400 440 search starting location guard band guard band mu delay mu phase desired phase 07851-049 figure 49. typical mu phase characteristic plot at 2.4 gsps figure 49 maps the typical mu phase characteristic at 2.4 gsps vs. the 9-bit digital delay setting (mudel). the mu phase scaling is such that a value of 16 corresponds to 180 degrees. the critical keep-out window between the digital and analog domains occurs at a value of 0 (but can extend out to 2 depending on the clock rate). the target mu phase (and slope) is selected to provide optimum ac performance while ensuring that the mu controller for any device can establish and maintain lock. for example, while a slope and phase setting of ?6 is considered optimum for operation between 1.6 gsps and 2.5 gsps, other values are required below 1.6 gsps. 0 2 4 6 8 10 12 14 16 18 0 40 80 120 160 200 240 280 320 360 400 440 delay line tap mu phase nom_p1 slow_p1 fast_p1 07851-050 figure 50. mu phase characteristics of three devices from different process lots at 1.2 gsps the mu phase characteristics can vary significantly among devices due to gm variations in the digital delay line that are sensitive to process skews (along with temperature and supply). as a result, careful selection of the target phase location is required such that the mu controller can converge upon this phase location for all devices. figure 50 shows that mu phase characteristics of three devices at 25c from slow, nominal, and fast skew lots at 1.2 gsps. note that a ?6 mu phase setting does not map to any delay line tap setting for the fast process skew case; therefore, another target mu phase is recommended at this clock rate. table 28 provides a list of recommended mu phase/slope settings over the specified clock range of the ad9739 based on the considerations previously described. these values should be used to ensure robust operation of the mu controller. table 28. recommended target mu phase settings vs. clock rate clock rate (gsps) slope mu phase 0.8 ? 6 0.9 ? 4 1.0 + 5 1.1 + 8 1.2 + 12 1.3 ? 12 1.4 ? 10 1.5 ? 8 1.6 to 2.5 ? 6
data sheet ad9739 rev. b | page 33 of 48 af ter the mu controller completes its search and establishes lock on the target mu phase, it attempts to maintain a constant timing relationship between the two clock domains over the specified temperature and supply range. if the mu controller requests a mu delay setting that exceeds the tapped delay line range (that is, <0 or >432), the mu controller can lose lock, causing possible system disruption (that is, can generate irq or restart the search). to avoid this scenario, symmetrical guard bands are recommended at each end of the mu delay range. the guard band scaling is such that one lsb of guard[4:0] (register 0x29) corresponds to eight lsbs of mudel (register 0x28). the recommended guard band setting of 11 (that is, register 0x29 = 0xcb) corresponds to 88 lsbs, thus providing sufficient margin. mu controller initialization description th e mu controller must be initialized and placed into track mode as a first step in the spi boot sequence. the following steps are required for initialization of the mu controller. note that the ad9739 data sheet specifications and characterization data are based on the following mu controller settings: 1. turn on the phase detector with boost (register 0x24 = 0x30). 2. enable the mu delay controller duty-cycle correction circuitry and specify the recommended slope for phase. (that is, register 0x25 = 0x80 corresponds to a negative slope). 3. specify search/track mode with a recommended target phase, set_phs, of 6 (for example) and an initial mudel[8:0] setting of 216 (register 0x27 = 0x46 and register 0x28 = 0x6c). 4. set search tolerance to exact and retry if the search fails its initial attempt. also, set the guard band to the recommended setting of 11 (register 0x29 = 0xcb). 5. set the mu controller tracking gain to the recommended setting and enable the mu controller state machine (register 0x26 = 0x03). upon completion of the last step, the mu controller begins a search algorithm that starts with an initial delay setting specified by the mudel register (that is, 216, which corresponds to the midpoint of the delay line). the initial search algorithm works by sweeping through different mu delay values in an alternating manner until the desired phase (that is, a set_phs of 4) is exactly measured. when the desired phase is measured, the slope of the phase measurement is then calculated and compared against the specified slope (slope = negative). if everything matches, the search algorithm is finished. if not, the search continues in both directions until an exact match can be found or a programmable guard band is reached in one of the directions. when the guard band is reached, the search still continues but only in the opposite direction. if the desired phase is not found before the guard band is reached in the second direction, the search changes back to the alternating mode and continues looking within the guard band. the typical locking time for the mu controller is approximately 180k dac cycles (at 2 gsps ~ 75 s). the search fails if the mu delay controller reaches the endpoints. the mu controller can be configured to retry (register 0x29, bit 6) the search or stop. for applications that have a microcontroller, the preferred approach is to poll the mu_lkd status bit (register 0x2a, bit 0) after the typical locking time has expired. this method allows the system controller to check the status of other system parameters (that is, power supplies and clock source) before reattempting the search (by writing 0x03 to register 0x26). for applications that do not have polling capabilities, the mu controller state machine should be reconfigured to restart the search in hopes that the systems condition that did not cause locking on the first attempt has disappeared. once the mu delay value is found that exactly matches the desired mu phase setting and slope (for example, 6 with a negative. slope), the mu controller goes into track mode. in this mode, the mu controller makes slight adjustments to the delay value to track any variations between the two clock paths due to temperature, time, and supply variations. two status bits, mu_lkd (register 0x2a, bit 0) and mu_lst (register 0x2a, bit 1) are available to the user to signal the existing status control loop. if the current phase is more than four steps away from the desired phase, the mu_lkd bit is cleared, and if the lock acquired was previously set, the mu_lst bit is set. should the phase deviation return to within three steps, the mu_lkd bit is set again while the mu_lst is cleared. note that this sort of event may occur if the main clock input (that is, dacclk) is disrupted or the mu controller exceeds the tapped delay line range (that is, <0 or >432). if lock is lost, the mu controller has the option of remaining in the tracking loop or resetting and starting the search again via the contrst bit (register 0x29, bit 5). continued tracking is the preferred state because it is the least disruptive to a system in which the ad9739 temporarily loses lock. the user can poll the mu delay and phase value by first setting the read bit high (register 0x26, bit 3). once the read bit is set, the mudel[8:0] bits and the set_phs[4:0] bits (register 0x27 and register 0x28) that the controller is currently using can be read.
ad9739 data sheet rev. b | page 34 of 48 interrupt requests the ad9739 can provide the host processor with an interrupt request output signal (irq) that indicates that one or more of the ad9739 internal controllers have achieved lock or lost lock. these controllers include the mu, data receiver, and synchronization controllers. the host can then poll the irq status register (register 0x04) to determine which controller has lost lock. the irq output signal is an active high output signal available on pin f13. if used, its output should be connected via a 10 k pull-up resistor to vdd33. each irq is enabled by setting the enable bits in register 0x03, which purposely has the same bit mapping as the irq status bits in register 0x04. note that these irq status bits are set only when the controller transitions from a false to true state. therefore, it is possible for the x_lck_irq and x_lst_irq status bits to be set when a controller temporarily loses lock but is able to reestablish lock before the irq is serviced by the host. in this case, the host should validate the present status of the suspect controller by reading back its current status bits, which are available in register 0x21 and/or register 0x2a. based on the status of these bits, the host can take appropriate action, if required, to reestablish lock. to clear an irq after servicing, it is necessary to reset relevant bits in register 0x03 by writing 0 followed by another write of 1 to reenable. a detailed diagram of the interrupt circuitry is shown in figure 51 . int(n) q d int source spi isr read data (pin f13) spi write int source spi address data = 1 imr sclk spi data 07851-051 figure 51. interrupt request circuitry it is also possible to use the irq during the ad9739 initialization phase after power-up to determine when the mu and data receiver controllers have achieved lock. for example, before enabling the mu controller, the mu_lck_en bit (register 0x03, bit 2) can be set and the irq output signal monitored to determine when lock has been established before continuing in a similar manner with the data receiver controllers. note that the relevant lck bit should be cleared before continuing to the next controller. after all controllers are locked, the lost lock enable bits (that is, x_lst_en) should be set. table 29. interrupt request registers address (hex) bit description 5 sync_lst_en 4 sync_lck_en 3 mu_lst_en 2 mu_lck_en 1 rcv_lst_en 0x03 0 rcv_lck_en 5 sync_lst_irq 4 sync_lck_irq 3 mu_lst_irq 2 mu_lck_irq 1 rcv_lst_irq 0x04 0 rcv_lck_irq 7 sync_trk_on 5 sync_lst 4 sync_lck 3 rcvr_trk_on 1 rcvr_lst 0x21 0 rcvr_lck 1 mu_lst 0x2a 0 mu_lkd
data sheet ad9739 rev. b | page 35 of 48 multiple device synchronization synchronization of multiple ad9739 s requires all of the devices to have matching pipeline delays. this implies the dac outputs are time aligned to the same phase when all devices are fed with the same data pattern at the same instance of time. the main contributor to phase ambiguity between devices is from the div-by-4 circuitry that drives the rx data path and data controller (see figure 53 ). this phase ambiguity can result in a 2 sample offset between any two devices. because the state of this internal divider is unknown at power-up, a synchronization method that phase aligns the digital paths of multiple ad9739 s is required to ensure matching pipeline delays. figure 52 shows a top-level diagram of multiple ad9739s synchronized to each other with sample alignment of the different data streams within the fpga (or among multiple fpgas) being assumed. a common rf clock source is distributed to each of the ad9739 devices via a dual clock buffer (such as the adclk946 ) with matched pcb trace lengths to each device to ensure matched propagation delays. one ad9739 is designated as the master providing a sync_out reference clock (equal to f dac /4) to itself as well as the other ad9739 slave devices sync_in input. lvds fanout buffers with matched output delays are again used to distribute the sync_out and dco signals of the master to the slave devices and fpgas, respectively, thus ensuring tight time alignment. note, in the case of a single fpga implementation (that is, i/q application), the dco of the master can drive the fpga directly. after synchronization, the internal div-by-4 circuitry will have equal phases that drive their respective lvds controllers. note, the mu and data receiver controller of both devices must be configured for the same spi register settings (that is, set_phs and dci_del) upon spi initialization such that controllers converge to similar delays. to validate that delays are roughly matched, the user can read back the delays of both devices (that is, mudel and dci_del) to determine if they are in an acceptable window that accounts for slight mismatches between different devices delay lines. fpga_1 matched delays to fpga_2 master dco to other fpgas to slave_1 to slave_n matched delays matched delays 1:n lvds repeater ad9739 master dco dacclk sync_in dci sync_out common clock source 0.8ghz to 2.0ghz dco adclk346 1:n lvds repeater ad9739 slave_1 dco dacclk sync_in dci sync_out ad9739 slave_n dco dacclk sync_in dci sync_out fpga_2 07851-052 figure 52. functional block diagram of two ad9739 s synchronized
ad9739 data sheet rev. b | page 36 of 48 90 0 db0[13:0] db1[13:0] dci db0 even db0 odd db1 even db1 odd dco f dac /4 sync_in sync_out div-by-4 0/180 rx data controller 90/270 state machine tracking loop phase rotator slave only to dac delay delay f dac mu delay mu delay f dac distribution synchronization controller phz mux 0 180 270 90 div-by-4 delay state machine tracking loop phase comparison 4:1 mux data assmbler 07851-053 f igure 53. top level block diagram of synchronization circuitry and controller figure 53 shows a top-level diagram of the synchronization controller (bottom) and how it interfaces to other digital functional blocks within the ad9739 . note the following observations of this top level diagram: ? synchronization between multiple devices is achieved by rotating the div-by-4 phases of the slave devices such that they align with the master. ? for the slave devices, the sync controller compares the phase alignment of the masters sync_in reference signal with the initial 0 o /90 o outputs of the div-by-4 and then rotates the div-by-4 phase until the sync_in signal falls between these phases. ? a reference signal common to all devices is required for synchronization. the master device generates this signal by providing a sync_out signal which is then distributed to all the devices (including itself with tight time alignment) as a sync_in signal. ? because the sync_in signal has a defined relationship between the div-by-4 phase of the master, the slave devices can now align their respective div-by-4 phases to the sync_in phase thus ensuring phase alignment among all devices. ? it is not possible to manually rotate the div-by-4 phases of the data path with the sync controller enabled. this can be a problem at lower clock rates were one may desire to rotate the div-by-4 phase to ensure locking of the data receiver controller and/or achieve a more optimum dci_del value. ? the dco output signal is generated from a separate div- by-4 circuit, and therefore, has a random phase upon each startup. for this reason, the dco of the master should be distributed to all the fpgas. sync controller initialization description the sync controller of the master is enabled by writing 0x70 to register 0x10. once enabled, a state machine automatically adjusts the output delay of its sync_out signal such that the fed back reference sync_in signal is centered between the 0 and 90 output phases associated with its div-by-4 circuit. note that the coarse delay is performed by shifting phases via phz mux while the fine delay that centers (and tracks) variation is done by a variable delay line. the variable delay line tap size is 12 ps. once sync_in is centered, the controller enters tracking mode such that sync_in remains centered despite possible system variations in temperature and/or supply. centering the sync_in signal on the master device ensures that the sync_in signals of the slave
data sheet ad9739 rev. b | page 37 of 48 devices also remain centered between their respective div-by-4 phases; therefore, providing the greatest margin to absorb nonideal timing skews. the following status bits are available in register 0x21 indicating lock, lost-lock, and tracking: sync_lck, sync_lst and sync_trk_on. t he sync controller of the slave is enabled by writing 0x50 to register 0x10. once enabled, the state machine compares the reference sync_in signal to the 0/90 phase outputs of the div-by-4 phase settings. if the sync_in signal does not fall between these phases, the state machine of the slave rotates the div- by-4 phase setting until it does. to validate that phase alignment has been achieved, the sync_in_ph90 and sync_in_ph0 status bits should read 1 and 0, respectively (that is, register 0x0d, bits[5:4]). note that the dco and sync_out outputs of the slave can be disabled via register 0x01, bit 5. s ynchronization limitations ensuring consistent synchronization over production lots in systems containing two or more ad9739 s becomes increasingly more challenging at the higher update rates because the timing offset between adjacent phases of the div-by-4 output clock is equal to 1/f dac . for example, a dac update of 2 gsps corresponds to a 500 ps period. if the sync_in signal of an ideal master device is positioned in the center of its div-by-4 0 o and 90 o phase outputs, only 250 ps of timing margin exists for the slave devices. this ideal margin is actually reduced by quadrature phase errors in the div-by-4 circuit of the master as well as its ability to position the sync_in exactly in the center of the 0 and 90 output phases. the timing margin is further eroded by the following sources: ? master-to-slave device(s) mismatch in the propagation delays in the mu delay clock path and sync_in. note that these mismatches can be up to 100 ps between devices that are at opposite extremes of the process corners. ? quadrature phase errors in the div-by-4 outputs of the slave. these sources of timing skews become more significant as the dacclk period is decreased (that is, clock rate is increased), leaving less margin for timing skews external to the master-to- slave device(s). special consideration to pcb layout and selection of clock distribution ics are required to ensure minimum skew between the distributed dacclk and sync_in signals. note that timing skews can quickly accumulate considering that the propagation delay on an fr4 pcb is on the order of 170 ps/inch, and that output-to-output skews on each clock distribution ic can be as high as 25 ps. the problem becomes more pronounced in multiboard synchronization where clock signals (that is, dacclk, sync_out, and dco) are distributed over a back plane to multiple pcbs. data alignment among the various data sources is required when driven by phase aligned dco signals that are a buffered version of the masters dco. however, these data sources (fpgas) also have process, supply voltage, and temperature sensitivities (pvts) that can cause misalignment among their respective dci outputs. adding to this dilemma is that it also possible for the data receiver controller of different ad9739 s to converge on different delay settings due to pvt variations of the delay line (even if dci inputs are exactly aligned). this can result in a four sample pipeline mismatch between devices if the difference in absolute delays exceeds a period of 4/f dac . recall that the controller searches up/down for its first valid edge from its initial start value (that is, dci_del and smp_del). while the initial start values between devices should be made the same, different absolute time delays due to pvt can cause devices to converge on different edges of dci above or below this initial start value. as a result, confirm that dci_del values between multiple devices are matched sufficiently such that the absolute differences between the readback dci_del values do not exceed a data period (that is, 4/f dac ). if the difference exceeds a data period, modify the dci_del (and smp_del) setting of the slave device so that its start point is roughly ? the difference between the master and slave readback values.
ad9739 data sheet rev. b | page 38 of 48 analog interface considerations analog modes of operation the ad9739 uses the quad-switch architecture shown in figure 54 . the quad-switch architecture masks the code-dependent glitches that occur in a conventional two-switch dac. figure 55 compares the waveforms for a conventional dac and the quad-switch dac. in the two-switch architecture, a code-dependent glitch occurs each time the dac switches to a different state (that is, d1 to d2). this code-dependent glitching causes an increased amount of distortion in the dac. in a quad-switch architecture (no matter what the codes are), there are always two switches transitioning at each half clock cycle, thus eliminating the code- dependent glitches. however, a constant glitch occurs at 2 dacclk because half of the internal switches change state on the rising dacclk edge, while the other half change state on the falling dacclk edge. v g 1 v dd ioutp ioutn v g 1 g 4 v g 3v g 2 dacclk_x clk latches dbx[13:0] v g 2 v g 3 v g 4 v 07851-054 figure 54. ad9739 quad-switch architecture inpu t data dacclk_x two-switch dac output four-switch dac output (normal mode) t d 1 d 2 d 3 d 4 d 5 d 6 d 7 d 8 d 9 d 10 d 6 d 7 d 8 d 9 d 10 d 1 d 2 d 3 d 4 d 5 d 6 d 7 d 8 d 9 d 10 d 1 d 2 d 3 d 4 d 5 t 07851-055 figure 55. two-switch and quad-switch dac waveforms another attribute of the quad-switch architecture is that it also enables the dac core to operate in one of the following three modes: normal mode, mix mode, and return-to-zero (rz) mode. the mode is selected via spi register 0x08, bits[1:0] with normal mode being the default value. in the mix mode, the output is effectively chopped at the dac sample rate. this has the effect of reducing the power of the fundamental signal while increasing the power of the images centered around the dac sample rate, thus improving the output power of these images. the rz mode is similar to the analog mix mode, except that the intermediate data samples are replaced with midscale values. input data dacclk_x four-switch dac output ( f s mix mode) four-switch dac output (return to zero mode) d 6 d 7 d 8 d 9 d 10 d 1 d 2 d 3 d 4 d 5 ?d 6 ?d 7 ?d 8 ?d 9 ?d 10 d 6 d 7 d 8 d 9 d 10 ?d 1 ?d 2 ?d 3 ?d 4 ?d 5 d 1 d 2 d 3 d 4 d 5 d 6 d 7 d 8 d 9 d 10 d 1 d 2 d 3 d 4 d 5 t t 07851-056 figure 56. mix-mode and rz dac waveforms figure 56 shows the dac waveforms for both the mix mode and the rz mode. note that the disadvantage of the rz mode is the 6 db loss of power to the load because the dac is only functioning for ? the dac update period. this ability to change modes provides the user the flexibility to place a carrier anywhere in the first three nyquist zones, depending on the operating mode selected. switching between the analog modes reshapes the sinc roll-off inherent at the dac output. the maximum amplitude in all three nyquist zones is impacted by this sinc roll-off, depending on where the carrier is placed (see figure 57 ). as a practical matter, the usable bandwidth in the third nyquist zone becomes limited at higher dac clock rates (that is, >2 gsps) when the output bandwidth of dac core and the interface network (that is, balun) contributes to additional roll-off. frequency (hz) 0fs 1.50fs 1.25fs 1.00fs 0.75fs 0.50fs 0.25fs ?35 ?30 ?25 ?20 ?15 ?10 ?5 0 first nyquist zone second nyquist zone third nyquist zone mix mode rz mode dbfs normal mode 07851-057 figure 57. sinc roll-off for each analog operating mode
data sheet ad9739 rev. b | page 39 of 48 clock input considerations the quality of the clock source and its drive strength are important considerations in maintaining the specified ac performance. the phase noise and spur characteristics of the clock source should be selected to meet the target application requirements. phase noise and spurs at a given frequency offset on the clock source are directly translated to the output signal. it can be shown that the phase noise characteristics of a reconstructed output sine wave are related to the clock source by 20 log10 (f out /f clk ) when the dac clock path contribution, along with thermal and quantization effects, are negligible. the ad9739 clock receiver provides optimum jitter performance when driven by a fast slew rate originating from the lvpecl or cml output drivers. for a low jitter sinusoidal clock source, the adclk914 can be used to square-up the signal and provide a cml input signal for the ad9739 clock receiver. note that all specifications and characterization presented in the data sheet are with the adclk914 driven by a high quality rf signal generator with the clock receiver biased at a 800 mv level. a dc blocking capacitor is used between the clock driver output and clock receiver input to allow for different dc bias levels. to minimize signal loss for high clock rates, a high quality, dc blocking rf capacitor is recommended. figure 60 shows a clock source based on the adf4350 low phase noise/jitter pll. the adf4350 can provide output frequencies from 140 mhz up to 4.4 ghz with jitter as low as 0.5 ps rms. each single-ended output can provide a squared-up output level that can be varied from ?4 dbm to +5 dbm allowing for >2 v p-p output differential swings. the adf4350 also includes an additional cml buffer that can be used to drive another ad9739 device. esd dacclk_p dacclk_n vddc vssc clkx_offset dir_x = 0 clkx_offset dir_x = 0 4-bit pmos iout array 4-bit nmos iout array 07851-060 figure 58. clock input and common-mode control the ad9739 clock receiver features the ability to independently adjust the common-mode level of its inputs over a span of 100 mv centered about its midsupply point (that is, vddc/2) as well as an offset for hysteresis purposes. figure 58 shows the equivalent input circuit of one of the inputs. esd diodes are not shown for clarity purposes. it has been found through characterization that the optimum setting is for both inputs to be biased at approximately 0.8 v. this can be achieved by writing a 0x0f (corresponding to a ?15) setting to both cross controller registers (that is, register 0x22 and register 0x23). d d q v cc v ee v t q v ref 50? 50 ? 50? 50 ? 50? dacclk_p dacclk_n 100 ? 1nf 1nf adclk914 ad9739 10nf 10nf 50 ? 07851-058 figure 59. adclk914 interface to the ad9739 clk input vco pll adf4350 fref 1.8v p-p v vco 1nf 1nf ad9739 3.9nh rf out a? rf out a+ rf out a? rf out a+ 100 ? dacclk_p dacclk_n div-by-2 n n = 0 ? 4 07851-059 figure 60. adf4350 interface to the ad9739 clk input
ad9739 data sheet rev. b | page 40 of 48 0.70 0.75 0.80 0.85 0.90 0.95 1.00 1.05 1.10 ?15 ?13 ?11 ?9 ?7 ?5 ?3 ?1 1 3 5 7 9 11 13 15 offset code common-mode (v) clkp clkn 07851-061 figure 61. common-mode voltage with respect to clkp_offset/clkn_offset and dir_p/dir_n voltage reference the ad9739 output current is set by a combination of digital control bits and the i120 reference current, as shown in figure 62 . current scaling fsc[9:0] ad9739 dac ifull-scale 10k ? 1nf v ref i120 agnd i120 v bg 1.2v + ? 07851-062 f igure 62. voltage reference circuit t he reference current is obtained by forcing the band gap voltage across an external 10 k resistor from i120 (pin b14) to ground. the 1.2 v nominal band gap voltage (vref) generates a 120 a reference current in the 10 k resistor. note the following constraints when configuring the voltage reference circuit: x both the 10 k resistor and 1 nf bypass capacitor are required for proper operation. x adjusting the output full-scale current, i outfs , of the dac from its default setting of 20 ma should be performed digitally. x the ad9739 is not a multiplying dac. modulating the reference current, i120, with an ac signal is not supported. x the band gap voltage appearing at vref (pin c14) must be buffered for use with external circuitry because its output impedance is approximately 5 k. x an external reference can be used to overdrive the internal reference by connecting it to vref (pin c14). i outfs can be adjusted digitally over 8.7 ma to 31.7 ma by using fsc[9:0] (register 0x06 and register 0x07). the following equation relates i outfs to the fsc[9:0] register, which can be set from 0 to 1023: i outfs = 22.6 fsc [9:0]/1000 + 8.7 (1) note that a default value of 0x200 generates 20 ma full scale, which is used for most of the characterization presented in this data sheet (unless noted otherwise). analog outputs equivalent dac output and transfer function the ad9739 provides complementary current outputs, ioutp and ioutn, that source current into an external ground reference load. figure 63 shows an equivalent output circuit for the dac. note that, compared to most current output dacs of this type, the ad9739 outputs exhibit a slight offset current (that is, i outfs /16), and the peak differential ac current is slightly below i outfs /2 (that is, 15/32 i outfs ). 17/32 i outfs i peak = 15/32 i outfs ac 70? 2.2pf i outfs = 8.6 ? 31.2ma 17/32 i outfs 07851-063 figure 63. equivalent dac output circuit as shown in figure 63 , the dac output can be modeled as a pair of dc current sources that source a current of 17/32 i outfs to each output. a differential ac current source, i peak, is used to model the signal-dependent nature of the dac output. the polarity and signal dependency of this ac current source are related to the digital code by the following equations: f ( code ) = ( daccode ? 8192)/8192 (2) ?1 f ( code ) < 1 (3) where daccode = 0 to 16,383 (decimal). because i peak can swing (15/32) i outfs , the output currents measured at ioutp and ioutn can span from i outfs /16 to i outfs . however, because the ac signal-dependent current component is complementary, the sum of the two outputs is always constant (that is, ioutp + ioutn = (34/32) i outfs ). the code-dependent current measured at the ioutp (and ioutn) output is as follows: ioutp = 17/32 i outfs + 15/32 i outfs f ( code ) (4) ioutn = 17/32 i outfs ? 15/32 i outfs f ( code ) (5)
data sheet ad9739 rev. b | page 41 of 48 figure 64 shows the ioutp vs. daccode transfer function when i outfs is set to 19.65 ma. i f the ad9739 is programmed for i outfs = 20 ma, its peak ac current is 9.375 ma and its peak power delivered to the equivalent load is 2.2 mw (that is, p = i 2 r). because the source and load resistance seen by the 1:1 balun are equal, this power is shared equally; therefore, the output load receives 1.1 mw or 0.4 dbm. 20 18 10 12 14 16 output current (ma) 8 6 4 2 0 0 4096 8192 12,288 dac code 16,384 07851-064 to calculate the rms power delivered to the load, the following must be considered: ? peak-to-rms of the digital waveform ? any digital backoff from digital full scale ? the dacs sinc response and nonideal losses in external network for example, a reconstructed sine wave with no digital backoff ideally measures ?2.6 dbm because it has a peak-to-rms ratio of 3 db. if a typical balun loss of 0.4 dbm is included, ?3 dbm of actual power can be expected in the region where the sinc response of the dac has negligible influence. increasing the output power is best accomplished by increasing i outfs , although any degradation in linearity performance must be considered acceptable for the target application. figure 64. gain curve for fsc[9:0] = 512, dac offset = 1.228 ma p eak dac output power capability t he maximum peak power capability of a differential current output dac is dependent on its peak differential ac current, i peak , and the equivalent load resistance it sees. because the ad9739 includes a differential 70 resistance, it is best to use a doubly terminated external output network similar to what is shown in figure 65 . in this case, the equivalent load seen by the ac current source of the dac is 25 . i peak = 15/32 i outfs ac 70 ? i outfs = 8.6 ? 31.2ma 180 ? r load = 50 ? r source = 50 ? lossless balun 1:1 07851-065 figure 65. equivalent circuit for determining maximum peak power to a 50 load
ad9739 data sheet rev. b | page 42 of 48 output stage configuration the ad9739 is intended to serve high dynamic range applications that require wide signal reconstruction bandwidth (that is, docsis cmts) and/or high if/rf signal generation. optimum ac performance can only be realized if the dac output is configured for differential (that is, balanced) operation with its output common-mode voltage biased to analog ground. the output network used to interface to the dac should provide a near 0 dc bias path to analog ground. any imbalance in the output impedance between the ioutp and ioutn pins results in asymmetrical signal swings that degrade the distortion performance (mostly even order) and noise performance. component selection and layout are critical in realizing the performance potential of the ad9739. mini-circuits ? tc1-33-75g+ 90 ? 90 ? ioutp ioutn 70 ? 07851-066 figure 66. recommended balun for wi deband applications with upper bandwidths of up to 2.2 ghz most applications requiring balanced-to-unbalanced conversion can take advantage of the ruthroff 1:1 balun configuration shown in figure 66 . this configuration provides excellent amplitude/phase balance over a wide frequency range while providing a 0 dc bias path to each dac output. also, its design provides exceptional bandwidth and can be considered for applications requiring signal reconstruction of up to 2.2 ghz. the characterization plots shown in this data sheet are based on the ad9739 evaluation board, which uses this configuration. figure 67 compares the measured frequency response for normal and mix mode using the ad9739 evaluation board vs. the ideal frequency response. ?36 ?33 ?30 ?27 ?24 ?21 ?18 ?15 power (dbc) ?12 ?9 ?6 ?3 0 0 500 1000 1500 2000 2500 3000 3500 frequency (mhz) ideal baseband mode mix mode tc1-33-75g baseband tc1-33-75g ideal mix mode 07851-067 figure 67. measured vs. ideal frequency response for normal (baseband) and mix mode operation using a tc1-33-75g transformer on the ad9739 evaluation board figure 68 shows an interface that can be considered when interfacing the dac output to a self-biased differential gain block. the inductors shown serve as rf chokes (l) that provide the dc bias path to analog ground. the value of the inductor, along with the dc blocking capacitors (c), determines the lower cutoff frequency of the composite pass-band response. an rf balun should also be considered before the rf differential gain stage and any filtering to ensure symmetrical common-mode impedance seen by the dac output while suppressing any common-mode noise, harmonics, and clock spurs prior to amplification. 90 ? ioutp ioutn 70? l l rf diff amp c c optional balun and filter 90 ? lpf 07851-068 figure 68. interfacing the dac output to the self-biased differential gain stage for applications operating the ad9739 in mix mode with output frequencies extending beyond 2.2 ghz, the circuits shown in figure 69 should be considered. the circuit in figure 69 uses a wideband balun with a configuration similar to the one shown in figure 68 to provide a dc bias path for the dac outputs. the circuit in figure 70 takes advantage of ceramic chip baluns to provide a dc bias path for the dac outputs while providing excellent amplitude/phase balance over a narrower rf band. these low cost, low insertion loss baluns are available for different popular rf bands and provide excellent amplitude/ phase balance over their specified frequency range. c c mini-circuits tc1-1-462m 90? ioutp ioutn 70? l l 90? 07851-069 figure 69. recommended mix mode co nfiguration offering extended rf bandwidth using a tc1-1-43a+ balun murata johanson technology chip baluns 180? ioutp ioutn 70 ? 07851-070 figure 70. lowest cost and size config uration for narrow rf band operation
data sheet ad9739 rev. b | page 43 of 48 nonideal spectral artifacts the ad9739 output spectrum contains spectral artifacts that are not part of the original digital input waveform. these non- ideal artifacts included harmonics (including alias harmonics), images, and clock spurs. figure 71 shows a spectral plot of the ad9739 within the first nyquist zone (that is, dc to f dac /2) reconstructing a 650 mhz, 0 dbfs sine wave at 2.4 gsps. besides the desired fundamental tone at the ?7.8 dbm level, the spectrum also reveals these nonideal artifacts that also appear as spurs above the measurement noise floor. because these nonideal artifacts are also evident in the second and third nyquist zones during mix mode operation, the effects of these artifacts should also be considered when selecting the dac clock rate for a target rf band. ?100 ?90 ?80 ?70 ?60 ?50 ?40 ?30 ?20 ?10 0 0 200 400 600 800 1000 1200 power (dbc) frequency (mhz) hd3 hd5 hd9 hd6 hd4 fund at ?7.6dbm f dac /4 ? f out f dac /2 ? f out f dac /4 3/4 f dac /4 ? f out hd2 07851-071 figure 71. spectral plot note the following important observations pertaining to these nonideal spectral artifacts: 1. a full-scale sine wave (that is, single-tone) typically represents the worst-case condition because it has a peak-to-rms ratio of 3 db and is unmodulated. harmonics and aliased harmonics of a sine wave are easy to identify because they also appear as discrete spurs. significant characterization of a high speed dac is performed using single (or multitone) signals for this reason. 2. modulated signals (that is, am, pm, or fm) do not appear as spurs but rather as signals whose power spectral density is spread over a defined bandwidth determined by the modulation parameters of the signals. any harmonics from the dac spread over a wider bandwidth determined by the order of the harmonic and bandwidth of the modulated signal. for this reason, harmonics often appear as slight bumps in the measurement noise floor and can be difficult to discern. 3. images appear as replicas of the original signal, therefore, can be easier to identify. in the case of the ad9739 , internal modulation of the sampling clock at intervals related to f dac /4 generate image pairs at ? f dac , ? f dac , and ? f dac . both upper and lower sideband images associated with ? f dac fall within the first nyquist zone, while only the lower image of ? f dac and ? f dac fall back. note that the lower images appear frequency inverted. the difference in dbc between the fundamental and various images remains mostly signal independent because the mechanism causing these images is related to corruption of the sampling clock. 4. the magnitude of these images for a given device is dependent on several factors including dac clock rate, output frequency, mu controller phase setting, and div-by-4 clock divider phase (register 0x14, bit [7:6]. table 30 shows how the magnitude of these images vary as the phase is varied for the case represented in figure 71 . because the phase varies at power up, the image magnitude varies making it difficult to compensate digitally through a one-time factory calibration procedure. also, the image magnitude can vary a few decibels over temperature and between devices due to process dependencies. (note that the ad9739a is a viable option if factory calibration is considered acceptable for nonmultichip synchronization applications operating with clock rates in the 1.6 gsps to 2.5 gsps range). table 30. image magnitude vs. phase (phz) setting image location phz0 phz1 phz2 phz3 f dac /4 ? f out ?70.2 ?71.4 ?72.2 ?77.1 f dac /2 ? f out ?80.2 ?71.3 ?69.9 ?74.9 ? f dac ? f out ?69.9 ?72.5 ?73.4 ?73.7 5. a clock spur appears at f dac /4 and integer multiples of this frequency. similar to images, the spur magnitude is also dependent on the same factors that cause variations in image levels. however, unlike images and harmonics, clock spurs always appear as discrete spurs, albeit their magnitude shows a slight dependency on the digital waveform and output frequency. note that the clock spur appearing at f dac /4 can also be factory calibrated. 6. a large clock spur also appears at 2 f dac in either normal or mix mode operation. this clock spur is due to the quad switch dac architecture causing switching events to occur on both edges of f dac .
ad9739 data sheet rev. b | page 44 of 48 lab evaluation of the ad9739 figure 72 shows a recommended lab setup that was used to characterize the performance of the ad9739 . the dpg2 is a dual port lvds/cmos data pattern generator available from analog devices, inc., with an up to 1.25 gsps data rate. the dpg2 directly interfaces to the ad9739 evaluation board via tyco z-pack hm-zd connectors. a low phase noise/jitter rf source, such as an r&s sma100a signal generator, is used for the dac clock. a 5 v power supply is used to power up the ad9739 evaluation board, and sma cabling is used to interface to the supply, clock source, and spectrum analyzer. a usb 2.0 interface to a host pc is used to communicate to both the ad9739 evaluation board and the dpg2. a high dynamic range spectrum analyzer is required to evaluate the ad9739 reconstructed waveforms ac performance. this is especially the case when measuring aclr performance for high dynamic range applications, such as multicarrier docsis cmts applications. harmonic, sfdr, and imd measurements pertaining to unmodulated carriers can benefit by using a sufficiently high rf attenuation setting because these artifacts are easy to identify above the spectrum analyzer noise floor. however, reconstructed waveforms having modulated carrier(s) often benefit from the use of a high dynamic range rf amplifier and/or passive filters to measure close-in and wideband aclr performance when using spectrum analyzers of limited dynamic range. adi pattern generator dpg2 ad9739 eval. board rhode and schwartz sma 100a agilent psa e4440a 10 mhz refin 10 mhz reout lab pc usb 2.0 gpib lvds data and dci dco 1.6ghz to 2.5ghz 3dbm power supply +5v 07851-072 figure 72. lab test setup used to characterize the ad9739 power dissipation and supply domains the power dissipation of the ad9739 is dependent on the dac clock rate as shown in figure 73 and figure 74 . the current consumption from the 3.3 v supply remains relatively constant because it is used for biasing the dac core (that is, vdda) and differential input receivers (that is, vdd33). however, the current consumption from the 1.8 v supply is clock rate dependent and increases linearly with frequency because this supply is used by the digital path (that is, vdd) as well as the clock distribution circuitry (that is, vddc). treat the vddc supply as an analog supply because the clock distribution circuitry has poor power supply rejection; therefore, noise on this supply can induce clock jitter. to ensure low noise on this sensitive supply, use a separate 1.8 v regulator powered from the 3.3 v analog supply rail that is also used to power vdda. this supply rail can also be used to power-up vdd33 via an lc filter network. the digital 1.8 v supply, vdd, can be supplied via a well-filtered switching regulator. 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 1.1 1.2 0 250 500 750 1000 1250 1500 1750 2000 2250 2500 total vdd vddc vdda vdd33 f dac (mhz) power (w) 07851-073 figure 73. power consumption vs. f dac @ 25c 0 30 60 90 120 150 180 210 240 270 300 330 360 0 250 500 750 1000 1250 1500 1750 2000 2250 2500 i_vdd i_vddc i_vdda f dac (mhz) current (ma) i_vdd33 07851-074 figure 74. current consumption vs. f dac @ 25c
data sheet ad9739 rev. b | page 45 of 48 r ecommended start-up sequence u pon power-up of the ad9739 , a host processor is required to initialize and configure the ad9739 via its spi port. figure 75 shows a flowchart of the sequential steps required, while tabl e 31 and table 32 provides more detail on the spi register write/read operations required to implement the flowchart steps. note the following: ? a software reset is optional because the ad9739 has both an internal por circuit and a reset pin. ? the sync controller is optional because it is only required to synchronize two or more devices. if synchronization is required, validate that dci_del values between devices are sufficiently matched . ? the mu controller must be first enabled (and in track mode) before the data receiver controller is enabled because the dco output signal is derived from this circuitry. ? a wait period is related to f data periods. ? limit the number of attempts to lock the controllers to three; locks typically occur on the first attempt. ? hardware or software interrupts can be used to monitor the status of the controllers. configure spi port software reset wait a few 100s configure mu cont. no yes yes yes set clk input cmv mu cont. locked? wait a few 100s configure sync cont. no sync cont. valid? wait a few 100s configure rx data cont. no rx data cont. locked? reconfigure txdac from default setting compare dci_del values sync. only optional 07851-075 figure 75. flowchart for initialization and configuration of the ad9739
ad9739 data sheet rev. b | page 46 of 48 table 31. recommended spi initializati on with sync controller disabled step address (hex) write value comments 1 0x00 0x00 configure for the 4-wire spi mode with msb. note that bits[7:5] must be mirrored onto bits[2:0] because the msb/lsb format can be unknown at power-up. 2 0x00 0x20 software reset to default spi values. 3 0x00 0x00 clear the reset bit. 4 0x22 0x0f 5 0x23 0x0f set the common-mode voltage of dacclk_p and dacclk_n inputs. 6 0x24 0x30 7 0x25 0x80 8 0x27 0x44 9 0x28 0x6c 10 0x29 0xcb 11 0x26 0x02 configure the mu controller. refer to table 28 for recommended target mu slope and phase settings vs. clock rate. 12 0x26 0x03 enable the mu controller search and track mode. 13 not applicable not applicable wait for 160 k 1/f data cycles. 14 0x2a read back register 0x2a and confirm that it is equal to 0x01 to ensure that the dll loop is locked. if it is not locked, proceed to step 10 and repeat. limit attempts to three before breaking out of the loop an d reporting a mu lock failure. 15 not applicable not appl icable ensure that the ad9739 is fed with dci clock input from the data source. 16 0x13 0x72 set fine_del_skew to 2. 17 0x10 0x00 disable the data rx controller before enabling it. 18 0x10 0x02 enable the data rx controller for loop and irq. 19 0x10 0x03 enable the data rx cont roller for search and track mode. 20 not applicable not applicable wait for 135 k 1/f data cycles. 21 0x21 read back register 0x21 and confirm that it is equal to 0x09 to ensure that the dll loop is locked and tracking. if it is not locked and tracking, advance the clkdivph[1:0] phase in register 0x14, bit[7:6] before proceeding to step 17 to repeat attempt. limit attempts to three before breaking out of the loop and reporting an rx data lock failure. 22 0x06, 0x07 0x00, 0x02 optional: modify the txdac i outfs setting (the default is 20 ma). 23 0x08 0x00 optional: modify the txdac operati on mode (the defaul t is normal mode).
data sheet ad9739 rev. b | page 47 of 48 table 32. recommended spi initializa tion with sync controller enabled step address (hex) write value comments 1 0x00 0x00 configure for the 4-wire spi mode with msb. note that bits[7:5] must be mirrored onto bits[2:0] because the msb/lsb format can be unknown at power-up. 2 0x00 0x20 software reset to default spi values. 3 0x00 0x00 clear the reset bit. 4 0x22 0x0f 5 0x23 0x0f set the common-mode voltage of dacclk_p and dacclk_n inputs. 6 0x24 0x30 7 0x25 0x80 8 0x27 0x44 9 0x28 0x6c 10 0x29 0xcb 11 0x26 0x02 configure the mu controller. refer to table 28 for recommended target mu slope and phase settings vs. clock rate. 12 0x26 0x03 enable the mu controller search and track mode. 13 not applicable not applicable wait for 160 k 1/f data cycles. 14 0x2a read back register 0x2a and confirm that it is equal to 0x01 to ensure that the dll loop is locked. if it is not locked, proceed to step 10 and repeat. limit attempts to three before breaking out of the loop an d reporting a mu lock failure. 15 0x15 0x42 configure sync controller. 16 0x10 0x00 disable sync controller before enabling it. 17 0x10 0x60 or 0x40 enable sync controller for loop and irq. 0x60 = master mode. 0x40 = slave mode. 18 0x10 0x70 or 0x50 enable sync controller: 0x70 = master mode. 0x50 = slave mode. 19 not applicable not applicable wait for 160 k 1/f data for dll to lock. 20 0x21 read back register 0x21 to confirm proper operation: 0x90 = master mode. 0x00 = slave mode. if not, proceed to step 15 and repeat. limit to three attempts before breaking out of loop and reporting sync lock failure. 21 0x0d read back register 0x0d and confirm bits[5:4] = 10. if not, proceed to step 2 and repeat. limit to three attempts before breaking o ut of loop and reporting sync lock failure. 22 not applicable not appl icable ensure that the ad9739 is fed with dci clock input from the data source. 23 0x13 0x72 set fine_del_skew to 2. 24 0x10 0x00 disable the data rx controller before enabling it. 25 0x10 0x02 enable the data rx controller for loop and irq. 26 0x10 0x03 enable the data rx cont roller for search and track mode. 27 wait for 135 k 1/f data cycles. 28 0x21 read back register 0x21 and confirm that it is equal to 0x09 to ensure that the dll loop is locked and tracking. if it is not locked and tracking, proceed to step 16 and repeat. limit attempts to three before breaking out of the loop and reporting an rx data lock failure. 29 not applicable not applicable readback dci_del value in register 0x13 and register 0x14 for master and. if slave devices are not within 40 codes of each other, re-specify target dci_del value to be average between master and readback dci_del value. 30 0x06, 0x07 0x00, 0x02 optional: modify the txdac i outfs setting (the default is 20 ma). 31 0x08 0x00 optional: modify the txdac operati on mode (the defaul t is normal mode).
ad9739 data sheet rev. b | page 48 of 48 outline dimensions 12.10 12.00 sq 11.90 0.43 max 0.25 min 1.00 max 0.85 min a b c d e f g h j k l m n p 14 13 12 11 10 8 7 6 3 2 1 9 5 4 1.40 max 0.55 0.50 0.45 10.40 bsc sq 11-18-2011-a compliant with jedec standards mo-275-ggaa-1. coplanarity 0.12 ball diameter 0.80 bsc detail a a1 ball corner a1 ball corner detail a bottom view top view seating plane figure 76. 160-ball chip scale package ball grid array [csp_bga] (bc-160-1) dimensions shown in millimeters ordering guide model 1 temperature range package description package option ad9739bbcz ?40c to +85c 160-ball chip scale package ball grid array [csp_bga] bc-160-1 ad9739bbczrl ?40c to +85c 160-ball chip scale package ball grid array [csp_bga] bc-160-1 ad9739bbc ?40c to +85c 160-ball chip scale package ball grid array [csp_bga] bc-160-1 ad9739bbcrl ?40c to +85c 160-ball chip scale package ball grid array [csp_bga] bc-160-1 AD9739-R2-EBZ evaluation board 1 z = rohs compliant part. ?2009C2012 analog devices, inc. all rights reserved. trademarks and registered trademarks are the property of their respective owners. d07851-0-1/12(b)

▲Up To Search▲

Price & Availability of AD9739-R2-EBZ

	To Download AD9739-R2-EBZ Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .